Print

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

I consider it an essential part of Dwaf Fortress, and can't play without it.

119 (18.4%)

I use it for pretty screenshots, but otherwise don't use it during play.

211 (32.7%)

I only try it occasionally.

174 (27%)

I have no idea why I'm even in this thread, I don't use it.

141 (21.9%)

Total Members Voted: 642

[therahedwig]

I thought the default was having detailed grass off...?

Either way, the grasses need to be configured more properly anyway. Right now it's half-defined in terrain and grasses both, and it should just be defined in grasses alone, so you can easily switch between 'super simple grass', 'animated grass' & 'detailed grass' (Anyone want the dark grass I made at one point in there as well?)(I could also make a variation where per biome one short grass picked and replaces all others within the biome, so per biome things will look more coherent. EDIT: Example. I already evened out the brightness in detailed grass tile in newer versions, and that helps a little as well)

This way, it should be easily configurable for a launcher or lazy newbie pack.

Furthermore, I learned a thing or two with the trees, and will probably add borders to the detailed grass at some point. (So at the least elevations will be more visible).

EDIT: BTW, it'll become more messier: With the new trees, a single tiles can have grass, leaves, blossom and fruit at the same time. If you only have the leaves visible, then you won't see the (useful) fruit...(and perhaps blossoms), so what will have priority here?

[Rose]

Priority there will be according to the sprite definition. You would probably just want to have fruits on top.

[therahedwig]

Priority there will be according to the sprite definition. You would probably just want to have fruits on top.

Ah! But what if you have two fruits at the same time?

In the meantime, I seperated the bark from the base-wood and am making bark for birches and later saguaros.
I'm going to treat Highwood as sequoias, everyone cool with that?

[Rose]

Each growth has a different ID.

Kumquat, for example, has:

LEAVES (kumquat leaf)
FLOWERS (kumquat flower)
FRUIT (kumquat)

while pine trees have:

LEAVES (pine needle)
SEED_CONE (pine seed cone)
POLLEN_CONE (pine pollen cone)

sprites would then be defined for each of these.

[therahedwig]

I was more wondering what would be expected if we have both a cherry and an apple on the same square. Display both? Display the top one?

Doesn't matter much really.

In the meantime:

SAGUARO!

[Rose]

The only way you can have a cherry and an apple on the same square is if we make a cherapple tree, and if you're going to go through that trouble, you may as well also make the stonesense sprites for it.

[Rose]

I was more wondering what would be expected if we have both a cherry and an apple on the same square. Display both? Display the top one?

Doesn't matter much really.

In the meantime:

SAGUARO!

Those are terrifying.

[therahedwig]

Those are terrifying.

Now you know why you fear the desert.

But yeah, DF saguaro branches don't go upward, only sideways. They do have fruit and flowers, but I'll need to embark on a desert to investigate how they attach to the main branch.

From the natural barks I only need to do palm, and then some palm folliage. And then it's time for feather trees and towercaps.

[Rose]

All growths have specific parts of the tree that they're set to grow from. I think this info can be gained from the raws, but I know how to get it from memory.

FLOWERS:
[lua]# ~df.global.world.raws.plants.all[194].growths[0].locations
<plant_growth.T_locations: 0x07ee675c>
twigs                    = false
light_branches           = false
heavy_branches           = false
trunk                    = true
roots                    = false
cap                      = false
sapling                  = false

FRUIT:
[lua]# ~df.global.world.raws.plants.all[194].growths[0].locations
<plant_growth.T_locations: 0x07ee675c>
twigs                    = false
light_branches           = false
heavy_branches           = false
trunk                    = true
roots                    = false
cap                      = false
sapling                  = false

[therahedwig]

Yeah, it's called 'growth_host_tile'.

I think I'll be able to come up with something.

[MarcAFK]

I was more wondering what would be expected if we have both a cherry and an apple on the same square. Display both? Display the top one?

Doesn't matter much really.

In the meantime:

SAGUARO!

Those are terrifying.

Dawww, they only want a hug!

[Rose]

Spoiler: So I got a thing working. (click to show/hide)

Column B is a token that you would set in the XML files.
Column C is what it actually gets matched up with.

This system will be moved over to everything that can change depending on material, though the old ways of assigning sprites will still work, unless something else over-writes them. (meaning a single <material token="INORGANIC*"/> will over-write every single inorganic material that's set the traditional way)

[Rose]

Spoiler: Tree material colors! (click to show/hide)

[Rose]

Spoiler (click to show/hide)

[therahedwig]

Spoiler: PRETTY TREES! (click to show/hide)

There's still a lot to be done of course, both on the sprite and coding side, but we're getting closer and closer!