Terrain bug on fortress
When a lava crawler (not sure what their actual name is, forgot to check) spawns in the ground on a slope, (or partially in a wall), the terrain below the mobs becomes 'flat' once they become attackable above ground, allowing the player to see through the world's terrain.
Image: https://imgur.com/a/EawCofl Last bumped on Jan 8, 2025, 3:20:56 AM
|
|
i got this same bug on trial of sekmas.. wasted another hour. feelsbad
|
|
Got the same shitty bug on my best run yet. Really frustrating this hole trial of smegma thing
|
|
same thing, decided to attempt 4th ascendancy, did flawless 0 hit run with amazing boons and barely any afflictions, was 100% sure thing to finish this run, started floor 4, got this, cannot enter, ?
|
|
Same situation. Put off 4th ascend due to the cumbersome nature of the new lab. Decided to give it a go today. Amazing run, amazing boons, amazing bug. It will be put off even longer due to the fear that this could happen again. Meanwhile, char is suffering with surivability issues, because the last nodes are Tailwind DR.
|
|
Bug still occuring right as you enter the fourth floor, I don't know how often it happens but it would be nice to see it fixed.
|
|
Mandatory sanctum without bug testing is insane. fire/move the ascendency guy please
|
|
Kind of tilting, this just happened to me as well.
|
|
Just happened to me on a special trial run on the 4th floor. I have so many questions, like are you just sending some encoded payload to the client that then generates the zone? If so, how could it be out of sync with the server. If you're doing a check against the generated terrain then why would you need to generate it independently in the first place? What kind of bizarre architecture is this lol. I mean I guess if you're passing a value to generate terrain and the client has a different version that generates different values then I can see you throwing an error but if you know where the terrain differs couldn't you just make it server authoritative and tell the client they failed the error check then stream the failed locations to the client to override their error'ed zones to match the server... unless its the server that is failing for some reason because of a bad value in the terrain generation in general in which case it has nothing to do with the values matching and more that the terrain generated in a way that hard failed, but in that case you're already catching the failure / error so couldn't you just suppress the warning to the user, generate a new value on error, then send that to your logs to fix later on? This just seems like the worse way to handle it man lol
I'm guessing the run is just straight dead and I need to try again and waste some divs on another relic. |
|
Hi GGG, are you there? Time to get back to work, kiddos. Paid-for products that you have released don't just fix themselves :)
nearly 3 weeks later and this bug is still happening during the cancer you have forced upon us that is Trials. This is required for 4th ascendency. For the love of god, please do something with your game's issues. |
|