Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Bask]

When embarking on a site (big cave, 3x3 goblin fortress, etc) that's bigger than the size you specify for your fortress (for example, 2x2), after embarking the fortress is the size of the pre-existing site. Put a 2x2 fortress in the middle of size 500 cave and the fortress automatically resizes to encompass it.

[Frobozz]

Sounds more like a feature than a bug. I know I wouldn't want to embark someplace only to discover a cave and then realize I can't explore the entire thing because I picked a size too small.

[Draco18s]

but...

ARGGH!! MY FPS!

[Toady One]

It can't (and likely won't ever) handle half-loaded sites, so it has to extend.

[Bask]

It can't (and likely won't ever) handle half-loaded sites, so it has to extend.

So that's a feature, thanks for the information.

[Aquillion]

Perhaps there could be a warning in the embark screen about this?

Obviously, for hidden things this could be a giveaway, so there could be an init option for whether or not you're warned in that case, or it could happen only when you have the 'prospector' functions turned on.

But a warning could be good, both to let people know it's not a bug and to warn people with slow machines that their FPS may take a hit if they embark there.