Print

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

[lethosor]

Yeah, everything writing text to files should do it in UTF-8. That isn't the default behavior for DF-encoded text, though, so many tool authors forget this. I'm not sure why it wasn't fixed when the encoding note was added.

[Fleeting Frames]

@lethosor: No particular attachment to make. Though I couldn't find ninja's minimum requirements at glance (I guess it might possibly want multi-core computer), no idea if they're significant for anyone.

[lethosor]

Neither could care less how many cores your computer has - the only difference is that Ninja uses multiple cores by default, while Make does not, but that's configurable with the -j option for both.

[PatrikLundell]

DFHack structure research request: Does anyone know how to look for volcanoes?

I know volcanoes are present as features, but when you view volcanoes pre embark they have names, which implies there should be a structure for them specifically akin to the one for rivers or the one for mountain peaks. A volcano structure also ought to contain the world tile coordinates of the volcano, and probably the mid level (region) tile coordinates within that tile as well.

The reason I'm looking for this data is that I've tried to hack a volcano in and then tried to embark on top of it, and DF has crashed every time. Apart from that, the volcano is visible only on the region view, not on the world tile level, which is another indication that there's something missing, and DF creates a region feature for the volcano where it feels like it, not where I want it (if I create it and move away from the tile, it's back where DF creates it when returning).

Edit: It looks like volcanoes are a special case of mountain peaks. It's possible flags[0] is "is_volcano".
Edit 2: And hacking in a "volcano" mountain peak caused a volcano to appear: the other structures were created automatically, and embarking on top of it worked. I've failed to see anything indicating which mid level tile the volcano would appear in, though.

[mifki]

I've failed to see anything indicating which mid level tile the volcano would appear in, though.

What?

[Meph]

Cant you simulate a volcano?  change the tiletype to open-space and magma flows, the edges to obsidian. Repeat for x zlvls till the magma lake is reached.

[PatrikLundell]

I've failed to see anything indicating which mid level tile the volcano would appear in, though.

What?

Mid level tile = the 16 * 16 tiles that make up a world tile. The term "mid level tile" is the one Toady used when asked in a FotF about what he called the different levels a year or two ago. Thus, a default embark covers 4*4 mid level tiles. (I assume that's what the rather terse "What?" was asking).

Cant you simulate a volcano?  change the tiletype to open-space and magma flows, the edges to obsidian. Repeat for x zlvls till the magma lake is reached.

Not pre embark, as the structure you'd hack hasn't been generated yet. I assume you could build a simulated "volcano" that way post embark, though, although I don't know if that would provide any magma rain to fill it. Anyway, that's not what I'm interested in doing.

[mifki]

I've failed to see anything indicating which mid level tile the volcano would appear in, though.

What?

Mid level tile = the 16 * 16 tiles that make up a world tile. The term "mid level tile" is the one Toady used when asked in a FotF about what he called the different levels a year or two ago. Thus, a default embark covers 4*4 mid level tiles. (I assume that's what the rather terse "What?" was asking).

Yep, thanks. I've never heard that and was rather confused thinking about z-levels or I don't know what. Don't we usually call them embark tiles?

[PatrikLundell]

They've also been called region tiles, although region tiles have also been used for a different level. Because of the risk for confusion, I've decided to adopt the terminology Toady provided when asked. I tried searching for Toady's answer, but failed to find it, though (I'm not very compatible with either the board or bug tracker search functions).

[Sorg]

They've also been called region tiles, although region tiles have also been used for a different level. Because of the risk for confusion, I've decided to adopt the terminology Toady provided when asked. I tried searching for Toady's answer, but failed to find it, though (I'm not very compatible with either the board or bug tracker search functions).

I think this is the answer you are talking about (it's from FotF 08.2017)

[mifki]

I think this is the answer you are talking about (it's from FotF 08.2017)

Ha ha, I'm not sure official names are useful -- they are often the worst names since the purpose of the structures has changed over the years, etc.  In any case, we have the 16x16 world tiles, which are called "feature shells" <...>

Nope I'm not ready to use "feature shells"

[PatrikLundell]

Thanks Sorg for digging up Toady's definitions.

I'm using "feature shells" when I need to refer to them, which isn't often, as the only case I know of is the weird organization of features.

[Tryble]

I just ran into the game-ending open-legends script bug described here.  The embark explodes in brutal fashion a little while after loading the save, revealing all tiles, regenerating the map, etc.  Odd, since it looks like this commit fixed that problem.

Anyway, judging from the comments in the issue page and related pages, I guess this save is done for?


To help any possible future searchers: Save is massively bugged, one a certain day the entire map is revealed, including HFS.  All dug stone is changed to undug stone as if the dwarves never mined out the fortress, and all buildings on the surface collapse.  The only tiles not replaced by their original stone are those which have items or dwarves standing in them.  In short, just about the entire embark is obliterated.  This is the same thing described in this reddit post, this mantis issue, and these DFHack threads.

[Meph]

Oh no. I just included a little workshop to run open-legends in my pack.  :-/

I hope this can be fixed, or i have to delete it again.

[comnom]

Hey guys, longtime player/luker/fan of DF and all her utilities.

Couple questions:

How interested would you guys be in an updated(graded) make-monarch script?
I've used the underlying logic to make the script applicable to all noble positions in entity.positions.own ("MONARCH", "DUKE", "COUNT", "BARON", "DIPLOMAT", "GENERAL", "LIEUTENANT", "CAPTAIN", "OUTPOST_LIAISON") and made it so that you can "demote" a unit without raising another.

Spoiler (click to show/hide)

Code: [Select]

local args = {...}
local argv = # args



function GetPositionID(entity, str)
local POSITIONS = {"MONARCH", "DUKE", "COUNT", "BARON", "DIPLOMAT",
"GENERAL", "LIEUTENANT", "CAPTAIN", "OUTPOST_LIAISON"}
local isValid = false
for i=0, 9 do
if POSITIONS[i] == str then
isValid = true
end
end
if not isValid then
qerror("Noble position '" .. str .. "' is not valid.")
end

for k, v in pairs(entity.positions.own) do
if v.code == str then
return v.id
end
end
return nil
end



function Demote(entity, posID)
for assignID, v in pairs(entity.positions.assignments) do
if v.position_id == posID then
local histFigOld = df.historical_figure.find(v.histfig)
if not histFigOld then
return
end
v.histfig = 0
for k,v in pairs(histFigOld.entity_links) do
local isInstance = df.histfig_entity_link_positionst:is_instance(v)
if isInstance and v.assignment_id == assignID and v.entity_id == df.global.ui.civ_id then
histFigOld.entity_links:erase(k)
return
end
end
end
end
end



function Promote(entity, posID, histFig)
for assignID, v in pairs(entity.positions.assignments) do
if v.position_id == posID then
v.histfig = histFig.id
histFig.entity_links:insert("#",
{new=df.histfig_entity_link_positionst,
entity_id=df.global.ui.civ_id,
link_strength=100,
assignment_id=assignID,
start_year=df.global.cur_year})
return
end
end
end



function Main()
local unit = dfhack.gui.getSelectedUnit()
if not unit then
qerror("Please select a unit.")
end

local histFig = dfhack.units.getNemesis(unit).figure
local ownEntity = df.historical_entity.find(df.global.ui.civ_id)

local posID = GetPositionID(ownEntity, string.upper(args[1]))
if not posID then
qerror("Could not find position ID.")
end

local isDemoting = false
if argv > 1 then
if string.lower(args[2]) == "demote" then
isDemoting = true
end
end
if isDemoting then
if not dfhack.units.isOwnGroup(unit) then
print("Can only demote this fort's units.")
else
Demote(ownEntity, posID)
end
else
Demote(ownEntity, posID)
Promote(ownEntity, posID, histFig)
end
end



Main()


(dead group barons borking my site's progression and "inhereted" barons were the impetus for the script if you were wondering).

I noticed the github repo doesn't have a contributing guidelines, so here I am rather than just doing a PR. Also the original make-monarch doesn't have any licensing attached to it, so while I'd be happy to release under a GNU GPLv3 I'm not quite sure if that's kosher.



With the above script in mind; What do we know about the event(s) concering elevating a fortress (barony/county/duchy)?

Ideally, I'd like to have the script elevate the fort if you assign a position you're not yet on, but I've failed in finding anything relevant.