Print

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

[Meph]

Does anyone have the updated version of 'startdwarf.rb' for 43.03? It states "patch address not available" atm.

Code: [Select]

# patch start dwarf count
=begin

startdwarf
==========
Use at the embark screen to embark with the specified number of dwarves.  Eg.
``startdwarf 500`` would lead to a severe food shortage and FPS issues, while
``startdwarf 10`` would just allow a few more warm bodies to dig in.
The number must be 7 or greater.

=end

nr = $script_args[0].to_i

raise 'too low' if nr < 7

addr = df.get_global_address('start_dwarf_count')
raise 'patch address not available' if addr == 0
df.memory_patch(addr, [nr].pack('L'))

[lethosor]

It's not the script that needs updating (the script hasn't changed in a long time), it's the offset that's missing. I guess nobody remembered to find it. I think the script to find it is working again, though, so it shouldn't be too hard.

[Roses]

So while looking through the entity tables I came across unknown1b.diplomacy and I am wondering if anyone has done any research on these values. It appears that there is(are) value(s) that determine how two entities feel about eachother. I was hoping to be able to use this to create more indepth diplomacy, but I don't know how to check what effect changing these has on the game. Anyone have any experience?

Code: [Select]

[lua]# ~df.global.world.entities.all[22].unknown1b.diplomacy[3]
<historical_entity.T_unknown1b.T_diplomacy: 0x0d31f1c8>
group_id                 = 18
relation                 = 1
anon_1                   = 174
historic_events          = <vector<int32_t>: 0x0d31f1d4>
historic_events_collection       = <vector<int32_t>: 0x0d31f1e4>
anon_2                   = 0

[wickys]

Has anyone found a way to make shells / horns / pearls / bones / skulls from certain creatures with the createitem command? Embarked on a barren embark without any creatures or fish and I wanna make bone/shell stuff.

Or even spawn animals itself.

I can't seem to use the spawnunit command because I don't know what caste is and anything I type in is invalid.

[Alluvian_Est-Endrati]

Has anyone found a way to make shells / horns / pearls / bones / skulls from certain creatures with the createitem command? Embarked on a barren embark without any creatures or fish and I wanna make bone/shell stuff.

Or even spawn animals itself.

I can't seem to use the spawnunit command because I don't know what caste is and anything I type in is invalid.

createitem should be able to produce creature-specific items. Have you checked the wiki for the command syntax: http://dwarffortresswiki.org/index.php/Utility:DFHack/createitem#Animal_products

For spawnunit (assuming the script is working properly) the caste is usually the gender. For example, the two castes for a pond turtle are MALE and FEMALE.

[wickys]

Yeah I did but the command is unclear to me.

item CREATURE_MAT:creature:material

It says.

What do I fill in item?

I know creature is CREATURE:COW for instance and material is BONE. But what is item?

I tried CORPSEPIECE but it said 'cannot create that type of item'.

I got to spawning animals now luckily but I'd rather get bones instead of animals who I then have to kill and butcher

[Alluvian_Est-Endrati]

My mistake, individual creature body parts cannot be created with createitem; such as if you wanted some quick bones for a strange mood. I thought you were aiming for items made out of specific creature materials. At the moment the best scenario would be to use spawnunit I believe.

[Bumber]

So I found the code responsible for parsing keybindings:

Code: (dfhack/library/Core.cpp) [Select]

if (keyspec.size() == 1 && keyspec[0] >= 'A' && keyspec[0] <= 'Z') {
        *psym = SDL::K_a + (keyspec[0]-'A');
        return true;
    } else if (keyspec.size() == 1 && keyspec[0] >= '0' && keyspec[0] <= '9') {
        *psym = SDL::K_0 + (keyspec[0]-'0');
        return true;
    } else if (keyspec.size() == 2 && keyspec[0] == 'F' && keyspec[1] >= '1' && keyspec[1] <= '9') {
        *psym = SDL::K_F1 + (keyspec[1]-'1');
        return true;
    } else if (keyspec.size() == 3 && keyspec.substr(0, 2) == "F1" && keyspec[2] >= '0' && keyspec[2] <= '2') {
        *psym = SDL::K_F10 + (keyspec[2]-'0');
        return true;
    } else if (keyspec == "Enter") {
        *psym = SDL::K_RETURN;
        return true;
    } else
return false;Looks like it only takes alphanumerics, function keys, and enter. How hard would it be to extend this to, let's say, all these SDL-supported keys?

Are there a lot of assumptions in the other code, or should any SDL key be handled just fine?

[Roses]

I'm looking for a way to specify not just an x,y,z in a given fort, but an x,y,z in the given world (basically I want to be able to check if a spot is the correct spot across the whole world, not just an embark site). I know there is df.global.world.map.region_x(y,z), but is that what I want to reference?

[mifki]

I'm looking for a way to specify not just an x,y,z in a given fort, but an x,y,z in the given world (basically I want to be able to check if a spot is the correct spot across the whole world, not just an embark site). I know there is df.global.world.map.region_x(y,z), but is that what I want to reference?

What do you mean "correct spot"?

[lethosor]

So I found the code responsible for parsing keybindings:

Code: (dfhack/library/Core.cpp) [Select]

if (keyspec.size() == 1 && keyspec[0] >= 'A' && keyspec[0] <= 'Z') {
        *psym = SDL::K_a + (keyspec[0]-'A');
        return true;
    } else if (keyspec.size() == 1 && keyspec[0] >= '0' && keyspec[0] <= '9') {
        *psym = SDL::K_0 + (keyspec[0]-'0');
        return true;
    } else if (keyspec.size() == 2 && keyspec[0] == 'F' && keyspec[1] >= '1' && keyspec[1] <= '9') {
        *psym = SDL::K_F1 + (keyspec[1]-'1');
        return true;
    } else if (keyspec.size() == 3 && keyspec.substr(0, 2) == "F1" && keyspec[2] >= '0' && keyspec[2] <= '2') {
        *psym = SDL::K_F10 + (keyspec[2]-'0');
        return true;
    } else if (keyspec == "Enter") {
        *psym = SDL::K_RETURN;
        return true;
    } else
return false;Looks like it only takes alphanumerics, function keys, and enter. How hard would it be to extend this to, let's say, all these SDL-supported keys?

Are there a lot of assumptions in the other code, or should any SDL key be handled just fine?

Coming up with names and translating them all would be tedious. There's probably some way we could make it easier, though, but relying on stuff like SysRq, Help, and Pause to be available probably isn't a good idea.

[Roses]

I'm looking for a way to specify not just an x,y,z in a given fort, but an x,y,z in the given world (basically I want to be able to check if a spot is the correct spot across the whole world, not just an embark site). I know there is df.global.world.map.region_x(y,z), but is that what I want to reference?

What do you mean "correct spot"?

Like imagine you have a spot in an embark at x,y,z. You then retire the fort and start an adventurer. How can you find that exact spot?

[John D]

It's not the script that needs updating (the script hasn't changed in a long time), it's the offset that's missing. I guess nobody remembered to find it. I think the script to find it is working again, though, so it shouldn't be too hard.

Has anybody who knows what script to use to find the offset looked that up yet?

[Bumber]

Coming up with names and translating them all would be tedious. There's probably some way we could make it easier, though, but relying on stuff like SysRq, Help, and Pause to be available probably isn't a good idea.

I was thinking of making a pair of arrays and using the names as shown on the page. The init would remain the same, except that "Enter" refers to numpad enter, not return. It's not a very long list with what's already handled.

Well, then only the ones on the page that intersect with DF.

Spoiler: Here's a quick WIP list: (click to show/hide)

Integer Pointer	| String
SDL::K_BACKSPACE	| BACKSPACE
SDL::K_TAB	| TAB
SDL::K_CLEAR	| CLEAR
SDL::K_RETURN	| RETURN
SDL::K_PAUSE	| PAUSE
SDL::K_ESCAPE	| ESCAPE
SDL::K_SPACE	| SPACE
SDL::K_EXCLAIM	| EXCLAIM
SDL::K_QUOTEDBL	| QUOTEDBL
SDL::K_HASH	| HASH
SDL::K_DOLLAR	| DOLLAR
SDL::K_AMPERSAND	| AMPERSAND
SDL::K_QUOTE	| QUOTE
SDL::K_LEFTPAREN	| LEFTPAREN
SDL::K_RIGHTPAREN	| RIGHTPAREN
SDL::K_ASTERISK	| ASTERISK
SDL::K_PLUS	| PLUS
SDL::K_COMMA	| COMMA
SDL::K_MINUS	| MINUS
SDL::K_PERIOD	| PERIOD
SDL::K_SLASH	| SLASH
SDL::K_COLON	| COLON
SDL::K_SEMICOLON	| SEMICOLON
SDL::K_LESS	| LESS
SDL::K_EQUALS	| EQUALS
SDL::K_GREATER	| GREATER
SDL::K_QUESTION	| QUESTION
SDL::K_AT	| AT
SDL::K_LEFTBRACKET	| LEFTBRACKET
SDL::K_BACKSLASH	| BACKSLASH
SDL::K_RIGHTBRACKET	| RIGHTBRACKET
SDL::K_CARET	| CARET
SDL::K_UNDERSCORE	| UNDERSCORE
SDL::K_BACKQUOTE	| BACKQUOTE
SDL::K_DELETE	| DELETE
SDL::K_KP0	| KP0
SDL::K_KP1	| KP1
SDL::K_KP2	| KP2
SDL::K_KP3	| KP3
SDL::K_KP4	| KP4
SDL::K_KP5	| KP5
SDL::K_KP6	| KP6
SDL::K_KP7	| KP7
SDL::K_KP8	| KP8
SDL::K_KP9	| KP9
SDL::K_KP_PERIOD	| KP_PERIOD
SDL::K_KP_DIVIDE	| KP_DIVIDE
SDL::K_KP_MULTIPLY	| KP_MULTIPLY
SDL::K_KP_MINUS	| KP_MINUS
SDL::K_KP_PLUS	| KP_PLUS
SDL::K_KP_ENTER	| KP_ENTER
SDL::K_KP_EQUALS	| KP_EQUALS
SDL::K_UP	| UP
SDL::K_DOWN	| DOWN
SDL::K_RIGHT	| RIGHT
SDL::K_LEFT	| LEFT
SDL::K_INSERT	| INSERT
SDL::K_HOME	| HOME
SDL::K_END	| END
SDL::K_PAGEUP	| PAGEUP
SDL::K_PAGEDOWN	| PAGEDOWN
SDL::K_F13	| F13
SDL::K_F14	| F14
SDL::K_F15	| F15
SDL::K_NUMLOCK	| NUMLOCK
SDL::K_CAPSLOCK	| CAPSLOCK
SDL::K_SCROLLOCK	| SCROLLOCK
SDL::K_RSHIFT	| RSHIFT
SDL::K_LSHIFT	| LSHIFT
SDL::K_RCTRL	| RCTRL
SDL::K_LCTRL	| LCTRL
SDL::K_RALT	| RALT
SDL::K_LALT	| LALT
SDL::K_RMETA	| RMETA
SDL::K_LMETA	| LMETA
SDL::K_LSUPER	| LSUPER
SDL::K_RSUPER	| RSUPER
SDL::K_MODE	| MODE
SDL::K_HELP	| HELP
SDL::K_PRINT	| PRINT
SDL::K_SYSREQ	| SYSREQ
SDL::K_BREAK	| BREAK
SDL::K_MENU	| MENU
SDL::K_POWER	| POWER
SDL::K_EURO	| EURO

Already handled keys omitted. We can remove entries as we confirm DF doesn't support them. (I probably spent way longer making this table that it would've taken to code..)

[Thundercraft]

What do you mean "correct spot"?

Like imagine you have a spot in an embark at x,y,z. You then retire the fort and start an adventurer. How can you find that exact spot?

If all you need is to find out the exact x,y,z of your embark site (or any other location, really), then why not use the Whereami script from Dirst's Accessibility Utility?

Quote:

whereami.lua
This script reports your current location as X, Y, Z coordinates and a very terse description of the tile such as "SOIL WALL" or "POOL FLOOR".
whereami will also report if the current location is recorded as a bookmark.