Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Darloth

9
Posts
3
Topics
2
Following
A member registered Jul 12, 2018

Recent community posts

Generally the cover and line of sight drawing seems fine, but I ran into this case on Arroyo where I am unsure it is correct.  Size 1 Everest and Size 1 Grunt Sniper, the book itself is unclear about any specific method of calculating whether something is hard cover or line of sight blocking and such... Here are two screenshots from an isometric angle and also the top down angle.  Hopefully it is replicable if you also think it's a problem.  Sortof related, some sort of line of sight checker hotkey would be lovely, and since that feature already exists for movement, making it something you can hold down while pointing at a given tile is presumably not -too- hard?  I assume this is on the to-do list already though, and certainly not vital for early builds.



Aaaaand only now have I found the -second- post explaining what you're doing.  Whoops, sorry!


I'll leave this thread here, but please reinterpret it as:

"I see you've not had time to do these things yet.  Is there any way I can help, or generally is there any modding it is possible to do?"

(1 edit)

I saw a much, much older thread about whether to use the Rebake NPCs, and want to mention my support for that. I also completely understand the viewpoint that it should be base corebook lancer first and foremost... it's not -my- preference, but it seems reasonable if that all needs to get done first.


Once they are done, I'd like to see the Rebake, or if it's too much work (probably a fair bit?) is there any way I can mod what's here now or in future to add them myself? I'm not totally unfamiliar with Godot if resources and code need to be changed for them, and I'm happy to give it a go even if it's complex, but equally if it's completely out of scope for the next while, that's very understandable.

This is total hearsay and guessing, but since you've also got nothing I figure it's worth mentioning - I had gone through the entire tutorial and also messed around a little with the scenario editor, but then not saved it, and earlier in the log are some errors about attempting to disconnect signals from non-existent callables, and sometimes connect signals to already-existing callables. They start on line 6493 if you're interested in those. Maybe something was called which was no longer valid, somehow, after all of my opening and closing and reopening of menus and things?
(1 edit)

Hi, got a game crash during instant action after playing around with the rest of the options and tutorial for a while.

The log file just cuts out half way through a line about creating a movement pathfinder.

I believe it happened half way through my turn, just after I'd used a lunge on an aux tactical knife, then triggered a turret drone reaction, then I was expecting to get the second aux knife in the mount but instead it crashed... Can't remember for sure though, and when I reloaded the autosave and tried to replicate the turn, obviously now I can't roll higher than 5 so I can't replicate the exact sequence of moves before the crash, but I did manage a lunge-into-turret-reaction-into-second-knife chain and that didn't crash this time, so I have no idea.


Here are the appropriate logs and custom pilots and saves: https://www.dropbox.com/scl/fi/j1xonl9lhvkqajhzx5z8v/lancertacticslogsetc.zip?rl...

Thanks for the long reply :)

Yeah, I knew that without having tested it I was risking all of the usual perils of analysis in a vacuum - I only made the comment because the Goliath seemed to be getting it both ways, less damage AND more fragile, and it didn't feel that the mobility or utility upgrade would compensate enough... but I've seen enough cases where actual play makes the read-through white room analysis basically useless to happily accept that you tested it and no it's fine really.  Thanks for placating my uncorroborated doomsaying, then!

(4 edits)

I love almost all of these, especially the rearrangement of reliable damage and the changes to the more generic seeming classes such as Assault and Rainmaker, but I have a major concern that the Goliath is far more fragile and also does a lot less damage.  It used to be a (perhaps somewhat overpowered) choice between getting through 25hp at long range where everything faces resistance, or coming within range 5 and risking being blasted by potentially triple 5 damage shotguns.  Your changes to it, while good overall, have made it very easy to either withstand the damage up close or destroy it from range - it's tougher than most but no longer a massive obstacle as it once was, which makes me worry it's going to be more of an ablative block of HP that only lasts a round or two, especially with even more taunt from the nicely upgraded Crush Target.  But... I also have not tried the change yet, so this is all speculative.  Have you or anyone tried the new Goliath a lot?  Can it really survive without Siege Plating? Should I just give it even MORE hp to make up for it?  Is this comment too long? (yes)

I'm sure it would be possible, if rather expensive.  Metal dice and faces with tiny magnets might work, or, possibly more effective and cheaper, just have a velcro die with velcro faces :)

Does it run in Wine or one of the many front-ends that make playing games via that route easier?  Graphically the game doesn't look complex, and optimized fps is not a concern, so I would expect it to be fine.  Haven't tried it myself yet of course.  (If you have no idea what I'm talking about, investigate Lutris)