Print

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

[doctorspoof]

Actually, I tell a lie.  It wasn't just with body parts that I've had save trouble.  Once during an upgrade I left out a weapon - couldn't open the save.  Another time I left out a stone - again, couldn't open the save.

By stone do you mean ore or just rock? 'cos if it's an ore, that's understandable, it's got all the reactions etc. to calculate. Much more complex than just normal rocks
Same thing goes for weapons as for limbs. Complex

[LegoLord]

The product of a reaction can exist without the reactant.  If an item tag in a reaction does not exist, it ignores that line of the reaction.  And ore reactions are based on the [ORE] tag in the rock's file, so if that tag is removed the stone is no longer an ore and therefore no longer has any reactions dependent on it.  Yes, it was an ore, but no, removing the tag that makes a stone an ore doesn't break old saves either; I switch mica's data with an ore once, and the save was fine (took all the stuff under the title and switched them; the titles had the same location).

The removal of an entry always breaks the save.  Always.

And weapons aren't that complex.  If stone worked the way you think it did, weapons would instead be replaced with "weapon" rather than breaking the save.  Stones have non-hardcoded data, just like weapons.

[doctorspoof]

The product of a reaction can exist without the reactant.  If an item tag in a reaction does not exist, it ignores that line of the reaction.  And ore reactions are based on the [ORE] tag in the rock's file, so if that tag is removed the stone is no longer an ore and therefore no longer has any reactions dependent on it.  Yes, it was an ore, but no, removing the tag that makes a stone an ore doesn't break old saves either; I switch mica's data with an ore once, and the save was fine (took all the stuff under the title and switched them; the titles had the same location).

The removal of an entry always breaks the save.  Always.

And weapons aren't that complex.  If stone worked the way you think it did, weapons would instead be replaced with "weapon" rather than breaking the save.  Stones have non-hardcoded data, just like weapons.

Both under the same title in the same location? As in, it could have been reading either of them? I don't quite understand what you're saying.
Weapons are complex, each civ entity has to have each tag for every weapon to allow them to wield it. Without the weapon there, the tag relates to nothing, therefore breaking the save. Bog-standard rocks don't get tagged for use by civilisations 
And i can tell stones have soft-coded data, that's why i was looking at their colours, symbols etc. in the raws.

[LegoLord]

I mean:
[MATGLOSS_STONE:MICA]
    [(data for other stone)]

Weapons are complex, each civ entity has to have each tag for every weapon to allow them to wield it. Without the weapon there, the tag relates to nothing, therefore breaking the save. Bog-standard rocks don't get tagged for use by civilisations 
And i can tell stones have soft-coded data, that's why i was looking at their colours, symbols etc. in the raws.

No, that is not how it works.  As stated before, tags that do not relate to anything are ignored.  I've messed around with stuff like that in reactions before, which are one of the most complicated things in DF - more so than weapons.

I just tried removing blowguns (which are not used by any civs in my game) and loading a game and got the message:  MISSING WEAPON DEFINITION: BLOWGUN.  The program then closed itself.

[doctorspoof]

I'm sure there would still be a blowgun somewhere on the world though, with it's specific damage, weight, etc.
Rocks all have equal weight etc, only difference is colour and layer they occur in.
If i was the game, and i had to pick one to be placeholded, i know which one i'd pick ^^

[LegoLord]

You're thinking like a person, not a program.  You have to think like a program.

So now I've taken out petrified wood.  Message:  MISSING STONE GLOSS:PETRIFIED_WOOD.

Is that good enough?

[doctorspoof]

Don't cry too much
Alright then, mr.-I-know-all-about-modding-DF, why has it randomly come up with this placeholder?
Why wouldn't it just fail to load up then?
A similar thing happened when i created a new creature, the cost free 'meat' item showed up on embark screens. I assume these incidents are linked, in a round-a-bout sort of way.
I've noticed this thread has turned into a rant between LegoLord and myself. This amuses me

[Vucar Fikodastesh]

why has it randomly come up with this placeholder?

Because the game couldn't find rock for the layers it was placing; the OP modded out all the stones except obsidian.

I had problems with the dreaded nullstone back when I was making my simplicity mod (which ended up getting far more complicated than it needed to be).  The fun thing is that you can make invisible things out of it.  The un-fun thing is that it weighs a ridiculous amount (this would be fun if you could drop stuff on enemies, but things don't quite work like that yet).

And yeah, it's just the game trying to create a hardcoded layer type when it doesn't have any types of stone that match that layer.  You don't even have to create duplicate entries, just slap all the stone layer types on obsidian and you'll be fine.

The simplicity mod works just fine with stone, sand and dirt.

It's probably hardcodedly attempting to put down a sedimentary layer and not finding any suitable rocks.  Try putting in duplicate obsidian entries with different occurence types (there's six of them, I think).

[doctorspoof]

why has it randomly come up with this placeholder?

Because the game couldn't find rock for the layers it was placing; the OP modded out all the stones except obsidian.

My point exactly. I think i may have mis-read the firstpost at first glance, thinking that by 'modding-out' it meant 'pimping-out'.

Another time I left out a stone - again, couldn't open the save.

Although, according to LegoLord, you're wrong, and the game shouldn't load up.

[Vucar Fikodastesh]

why has it randomly come up with this placeholder?

Because the game couldn't find rock for the layers it was placing; the OP modded out all the stones except obsidian.

My point exactly. I think i may have mis-read the firstpost at first glance, thinking that by 'modding-out' it meant 'pimping-out'.

Another time I left out a stone - again, couldn't open the save.

Although, according to LegoLord, you're wrong, and the game shouldn't load up.

No.

Legolord is talking about modifying the RAWs with an already generated world. I am not.

[LegoLord]

Yeah.  The placeholder stone only appears when generating a new world when the stone necessary does not exist.  If you don't gen a new world after that, you have no worlds you can play.

How much modding have you done doctorspoof, out of curiosity?

[doctorspoof]

I apologise, i thought you were talking about the same thing.

And i've made a few new creatures, new civilization, new materials, new weapons, etc.
Does it matter?

[LegoLord]

No, just wondering . . .

[. . .] mr.-I-know-all-about-modding-DF, [. . .]

(see sig)

Not everything, but in that mod's development, I have encountered many bugs and problems - most before its release.  Some of which relate somewhat to the thread's problem.

[doctorspoof]

*slaps on wrist*



 

[LegoLord]

*slaps on wrist*



 

Thank you.