Print

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

[milo christiansen]

Simply put, how do you get the material of a tile from it's coords? I really need to be able to tell if a building is built on sand or clay, and all I can seem to get is if it is built on soil.

[Protonicus]

I cannot help you directly.
But you may look at your df folder "dwarf fortress/hack/ruby/map.rb"
I found there smth similiar to your question.

Code: [Select]

def tilemat
     Tiletype::Material[tiletype]
end

def map_block_at(x, y=nil, z=nil)
      x = x.pos if x.respond_to?(:pos)
      x, y, z = x.x, x.y, x.z if x.respond_to?(:x)
      if x >= 0 and x < world.map.x_count and y >= 0 and y < world.map.y_count and z >= 0 and z < world.map.z_count
           world.map.block_index[x/16][y/16][z]
      end
end


[UristMcNoble]

Might be a bit late, but this will tell you what the material under the current cursor position is

Code: [Select]

df.map_tile_at(*df.cursor).mat_info.token

[Putnam]

uh what language is that

[Warmist]

uh what language is that

ruby

[Putnam]

I figured it was probably, but the snippet was too small for me to tell precisely. I mean, I was fairly confident, but ya gotta ask.

[Raidau]

probe plugin may be the answer, since it gets the tile material somehow. I wish to implement tile material related things in my mod

[milo christiansen]

Is there a Lua way to do that?

[Putnam]

Well, probe does it like so:

Code: [Select]

df::tiletype_material material = tileMaterial(tiletype);

tileMaterial is a function:

Code: [Select]

    inline
    df::tiletype_material tileMaterial(df::tiletype tiletype)
    {
        return ENUM_ATTR(tiletype, material, tiletype);
    }
And ENUM_ATTR is a function-like preprocessor macro:

Code: [Select]

#define ENUM_ATTR(enum,attr,val) (df::enum_traits<df::enum>::attrs(val).attr)
There's a lot more in probe, gimme a little bit. df.tiletype.attrs[num].material is most certainly a thing, at least.

EDIT: Wow this is complicated, heh. Hmm:

Code: [Select]

    /// Base layer material (i.e. layer stone, veins, feature stone)
    t_matpair baseMaterialAt(df::coord2d p)
    {
        if (!basemats) init_tiles(true);
        return t_matpair(
            index_tile<int16_t>(basemats->mat_type,p),
            index_tile<int16_t>(basemats->mat_index,p)
        );
    }
Okay. That's in MapCache, so apparently that may be needed.

[milo christiansen]

That's s far as I got too, MapCache is apparently not exported to Lua.

[lethosor]

I believe MapCache is only a wrapper, so you should be able to get the same data from map blocks directly (although I'm not exactly sure how).

[Raidau]

I believe MapCache is only a wrapper, so you should be able to get the same data from map blocks directly (although I'm not exactly sure how).

Yeah, blocks contain information about inorganics the tiles consist of. But the data structure there is complicated

[Warmist]

this part

Code: [Select]

#define ENUM_ATTR(enum,attr,val) (df::enum_traits<df::enum>::attrs(val).attr)
is actually exported to lua. I think it's "df.tiletype.attrs[tiletype]" or "df.tiletype._attrs[tiletype]".
So it would look like:

Code: [Select]

local ttype=dfhack.maps.getTileType(x,y,z)
local material=df.tiletype.attrs[ttype].material
or something like that...

[Putnam]

Yeah, I mentioned that.

There's a lot more in probe, gimme a little bit. df.tiletype.attrs[num].material is most certainly a thing, at least.

It doesn't really actually help though...

[Warmist]

Oh missed that. I guess we need to make an util for that.

The complexity arises because map does not have "materials". It has indication that this tile is of some type. And then if it's construction you need to look one place, if it's vein other place, trees are yet in another place, layer materials are from yet another place and so on...