Print

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

[Philii]

In Advanced World Creation, There is no End year validation(Except some).
I tired to baby siting world creation.

I got Idea about setting some custom validation for perform only one at end year.
Eg. Goblin World.=> by Setting minimum Goblin population desire or maximum. If not Auto-Reject.
Undead World.=> Minimum tower count.

[Shonai_Dweller]

Yeah. I always use "percentage of dead beasts" to end worldgen.
No fun adventuring if all the big bad stuff is long gone.
So it would be good to have more options there.
- Percentage of Fallen Civs
- Percentage of dead kobolds
Etc.

Not sure what the op means by auto-reject though?
I wouldn't want to wait a hundred years only to have my worldgen reset because there were too many goblins. Current system of checking then stopping worldgen at specific milestones is good.

[Philii]

I mean Re generate world from start until user interacted or found Desired world.
So that way I can find world while i sleep or do something. (Without wait watch reject and regenerate cycle)

[Shonai_Dweller]

I mean Re generate world from start until user interacted or found Desired world.
So that way I can find world while i sleep or do something. (Without wait watch reject and regenerate cycle)

Why would you need it to reset though?
What's wrong with just stopping when you reach the limit you set?

[PatrikLundell]

I think I understand what Philii is after: Start generation and then go to work/sleep/school/vacation to have something desired waiting when returning to the computer. Time isn't that much of an issue in that case. This would essentially be an advanced version of the current world gen where you specify the reject criteria in more detail. It might be tricky to get the criteria selection and implementation right though.

Shonai_Dweller's version of generating the current world until it reaches a desirable state can be achieved using a DFHack script to check the relevant details every tick (which mostly, but not always, matches a year), but it will eventually reach the specified end date if it failed to find the desired features.

If it's possible to indicate to DF that a world is rejected so it starts a new cycle from within a DFHack script (I don't know if that functionality is available), the same kind of script as the one suggested in the previous paragraph might be used here as well.

[Philii]

Why would you need it to reset though?
What's wrong with just stopping when you reach the limit you set?

Well, when every world reach limit i set, i export and check something i want in the world. ( some world without goblin or too far with goblin that world i dont need it.)
If not than delete, regenerate world. and than again wait, export, look.
Sometime I want world with many tower and goblin in advanced world gen, than wait , no tower, than stop, regenerate.
than after export i found no goblin, or no elf, or no human (or too many).(sometime very low population of GIANT CAVE SPIDER)

[Shonai_Dweller]

Oh, I understand now.
So what might be good is a combination. "Minimum desired or Reset" plus "dead beasts (etc) percentage and year to start checking"

If a world reaches the year limit without generating enough towers, it resets. But if it did exceed your number , and then Towers started being destroyed you could use the "dead beasts trigger" to trigger an end to worldgen (so long as it's over a certain desired minimum).

That'd give you more chance to get a very exact world by the time you wake up.