Print

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

[Hommit]

Any chance to someone updating digvx code, so it don't place SO many stairs (sometimes up to like 80% of tiles on one level!)?

[Putnam]

It places stairs wherever there's a vein of similar material on an adjacent z-level; I'd say it makes perfect sense to do it that way. It seems more of a personal issue.

[Askot Bokbondeler]

i don't use stairs, i'd prefer if it would place ramps. it wouldn't always work, but that's what overseers are for. how would i go about changing it?

[Mr S]

First step, set up a very efficient hospital for all of the upcoming mining injuries...

 

[peterix]

i don't use stairs, i'd prefer if it would place ramps. it wouldn't always work, but that's what overseers are for. how would i go about changing it?

The code for that is here:
https://github.com/peterix/dfhack/blob/master/plugins/dig.cpp#L987

Currently, it spreads up and down, setting the designations appropriately. If you wanted to do ramps, you'd have to do channels. A tile where the algorithm would spread down would be designated for channeling, a tile that would make it go up would NOT be designated. Everything else would be designated for normal digging. Nothing would change about the actual algorithm, just a few more conditions and different designations.

[cdombroski]

I've duplicated the upcoming restrictliquid and restrictice commands as lua scripts (thanks to rampaging-poet for the original code!). I imagine it's not as fast as the original C++ code, but it gets the job done for me.

Here they are for anyone else who's impatient like me:

Code: (restrictliquid.lua) [Select]

-- Restrict visible tiles with liquid
max_x,max_y,max_z = dfhack.maps.getTileSize()
for x=0, max_x-1 do
for y=0, max_y-1 do
for z=0, max_z-1 do
des = dfhack.maps.getTileFlags(x,y,z)
if des ~= nil and des['hidden'] == false and des['flow_size'] ~= 0 then
des['traffic'] = df.tile_traffic['Restricted']
end
end
end
end


Code: (restrictice.lua) [Select]

-- Restrict tiles over visible ice walls
max_x,max_y,max_z = dfhack.maps.getTileSize()
for x=0, max_x-1 do
for y=0, max_y-1 do
for z=1, max_z-1 do
des = dfhack.maps.getTileFlags(x,y,z)
des_below = dfhack.maps.getTileFlags(x,y,z-1)
type_below = dfhack.maps.getTileType(x,y,z-1)
if des_below ~= nil and des_below['hidden'] == false and type_below == df.tiletype['FrozenWall'] then
des['traffic'] = df.tile_traffic['Restricted']
end
end
end
end


[eclipse412]

How can I use this to fill in a hole with clay? I dug a hole to get ride of water then thought I could use this to fill it in. Any Help?
Thanks,
E

[scamtank]

Use tiletypes to transform the clay floor tiles into clay wall tiles.

"filter shape floor" and "paint shape wall" should be enough for settings. It'll transform any floor tile under the loo[k]-cursor into a plain undug wall of the same material.

[Askot Bokbondeler]

thanks!

[eclipse412]

What about open space?

[Kurik Amudnil]

unit.appearance.unk_4c8  is the effective body appearance modifier (percent), default is 100.  This effective body modifier is the result of combining the body size modifiers in unit.appearance.body_modifiers[] .  I haven't looked at enough creatures that use more than 2 modifiers to see if the integer division happens for each modifier or is applied later.  With body_modifiers 99 and 106, unk_4c8 = 104 = 99 * 106 / 100.

Using unk_4c8, my estimated body size calculation is now spot on for units that spawn full grown.

*edit: found a unit with modifiers 95,104,107, and unk_4c8 = 105

100 * 95/100 * 104/100 = 98.80 => 98 * 107 / 100 = 104.86 => 104 != 105

100 * (95 * 104 * 107) / 100^3 = 105.7160 => 105 == 105 so it looks like the loss of precision happens last rather than for each modifier

[Billy Jack]

https://github.com/expwnent/dfhack/blob/f92e859f499105abfbb40d008189bc36e88323f5/Readme.rst#mod-interaction

I have (finally) written the documentation for the NEXT version of autoSyndrome/syndromeTrigger. The rules are slightly different from the way they are now, but they make more sense this way and should only require minimal changes. The main changes: boiling temperature is now ignored, you need to have a \AUTO_SYNDROME tag, and instead of \WORKER_ONLY, there's \ALLOW_NONWORKER_TARGETS, which does the opposite of what \WORKER_ONLY did (it makes more sense for worker only to be the default).

The short version: autoSyndrome allows you to instantly attach syndromes to units with custom building reactions. syndromeTrigger lets you trigger commands or do true transformations whenever a unit becomes afflicted with a syndrome, regardless of the cause of the syndrome. It should work whether it's from "natural causes", an interaction, autoSyndrome, and hopefully even for itemsyndrome.

edit: also, both autoSyndrome and syndromeTrigger are disabled by default to help FPS for those who don't need it. It is recommended that if you want to use them you add the following to your dfhack.init file:

Code: [Select]

autoSyndrome enable
syndromeTrigger enable


While I'm not a pro on reading C++ code, it looks to me like the default of affecting the worker only will still result in other creatures possibly being affected.
https://github.com/expwnent/dfhack/blob/master/plugins/autoSyndrome.cpp

At line 382, the Boolean test on workeronly continues on in the For loop.  Shouldn't it exit the loop?  At the end of the For loop, a valid target is attempted to be found, with the worker being ignored.

I was trying to figure out why a baby was being affected when the mother tries to run the reaction.

[expwnent]

Each syndrome is treated separately. You can have multiple syndromes per rock, or multiple rocks per reaction.

edit: "continue" means "skip the rest of this iteration of the loop".

[Ranalcus]

Sorry to bother you guys.
But i have used th exportmaps command, and I don't know WHERE it was exported or what is the name of those map files. I Have a working Isoworld (after FEW problems) but I don't know how to use it, it is probably so simple that they even don't write it in readme...

;___;
Help

[ORCACommander]

well wrong place to ask for help with iso world but i have also used that script. it puts it out to where pictures always go, the df home directory.