Bay 12 Games Forum

I think it's a typo, it should be "designation".

Quote from: mifki on July 22, 2015, 05:33:45 pm

Quote from: expwnent on July 22, 2015, 05:22:55 pm

Quote from: mifki on July 22, 2015, 05:21:45 pm

What is the extra viewscreen_dwarfmodest for?

That makes it so that it works even if the current viewscreen is something else.

That's not required even in this case. Just use df.global.gview.view.child instead of getCurViewscreen() - it will correctly place the new screen on the top of the stack even if the parent screen wasn't on top.

You'd want to make sure that screen is actually a dwarf mode viewscreen, though. (Is this supposed to work in adventure mode?)

In my case it can be dwarf mode only.
Oh, right, if this script is supposed to work in adv mode, then creating a new dwarf mode screen is required.

What is the extra viewscreen_dwarfmodest for?

Quote from: mifki on July 21, 2015, 05:07:24 pm

With viewscreen_layer_arena_creaturest approach it's very easy to add equipment.

There are a number of issues with spawning intelligent creatures, at least if you want them to function as citizens of a civ.  The script above (if hacked to allow it) can spawn a new member of the fort, but he/she has no preferences or dreams or relationships.

Spawned creatures can be adopted as pets, so they can make NEW relationships.  The problem is that they start out with a slate that's a bit too blank.

Given those limitations, no one delved into equipment.

New dwarves created with viewscreen_layer_arena_creaturest have preferences.
But no relationships of course because it doesn't create a histfig.  On the other hand, relationships totally depend on what you're creating (civ member, pet, invader), so can't be created fully automatically.

I haven't done much work on it myself but I'm told that nemesis/histfig stuff is the hardest part to get working properly. As for code in the game you can use, there's always transformation + pregnancy, but that only works on races that can reproduce, it requires a unit to start with who isn't otherwise occupied with anything important, it can only be done across 3-4 frames, and if the game exits halfway through it might do horrible things to the save file.

Frames are just calls of viewscreen_dwarfmodest:logic(), we could call that from Lua.

I'll try, but again, I wasn't saying it would solve all the problems. You'll need to configure the unit afterwards to get the behaviour you want. But at least no need to deal with body/appearance/personality/next_ids and to worry about some of the data being uninitialised and thus causing problems.

There was a fairly recent version in the DFHack thread somewhere. I seem to remember that friendly creatures turn hostile after save/load with that version. I don't have a link, sorry.

I've created a dwarf and an aardvark with viewscreen_layer_arena_creaturest, the aardvark is still friendly after save/load, and the dwarf is still working in a workshop. Free workforce, yay!

Quote from: mifki on July 20, 2015, 11:56:27 pm

Quote from: lethosor on July 20, 2015, 11:02:41 pm

Oh, is it working now? Are nemesis entries handled? It would be nice to (re?)-add that to DFHack, since a lot of people have asked about it.

taldarus - creating units is not a simple task, largely because DFHack doesn't have access to the code DF uses (and it's unlikely that DF has code to create units from scratch in arbitrary locations in any case).

Can't you use viewscreen_layer_arena_creaturest? It doesn't create hf/nemesis, but seems to do everything else much easier than doing it manually.

I think the current version of the script is at least that functional.

Using the original DF code is just more reliable and much less code to write and maintain.