View Issue Details

IDProjectCategoryView StatusLast Update
0007871Dwarf FortressCreaturespublic2014-08-06 07:29
ReporterEldrickWT Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
PlatformSDLOSWindowsOS VersionVista 64
Product Version0.40.06 
Summary0007871: Several Tokens crash cause a CTD if in a CV_REMOVE_TAG token
Description4 Tokens and 1 Group of 3 Tokens will crash DF to desktop if built into a creature variation.

Individuals:
CV_REMOVE_TAG:CURIOUSBEAST_EATER
CV_REMOVE_TAG:CURIOUSBEAST_GUZZLER
CV_REMOVE_TAG:CURIOUSBEAST_ITEM
CV_REMOVE_TAG:DESCRIPTION
Group:
CV_REMOVE_TAG:MATERIAL
CV_REMOVE_TAG:MATERIAL_TEMPLATE
CV_REMOVE_TAG:MELTING_POINT


As it says in the forum thread (Additional Information Section Below)just wanted to slap together a C_V I could plop onto a species to remove CuriousBeast tokens... without hunting for them in the creature, and to be able to reuse it later on other creatures. After a mess of testing I found all the tokens above.

Kaboom without errorlog.
Steps To Reproducemake a creature variation file.
place any of the individual tokens above or the group of tokens in it.
place in a creature file "just about anywhere" within the creature's definition.
Go into Arena mode... when it parses the creatures you will CTD.

Alternately
place in a creature in a world's raw directory.
Load the world... when it parses the creatures you will CTD.
Additional InformationTesting thread. http://www.bay12forums.com/smf/index.php?topic=141881.0
TagsNo tags attached.

Relationships

related to 0006267 new Creature variations crash when trying to remove multiple tokens from the end of a creature entry 

Activities

EldrickWT

2014-08-06 07:29

reporter   ~0028442

Last edited: 2014-08-06 07:49

Lethsor having trouble reproducing the crashes has rekindled testing. Description is off the hook -I should have recalled it being in other C_V's just fine already- and I've found that 2 curiousbeast entries and the 3 M's are enough to crash a vanilla DF install. One will not do it, but any two was enough.

Seeing Knight Otu's relationship addition I'm going to try moving the apply and the apply current all over the creature to see if it continues being problematic.

Edit: Moving it around did stop the crashing. Reading the Newly Added Relationship I added a fresh section to the base of the creature:

    [SELECT_MATERIAL:BLOOD]
     [PLUS_MATERIAL:PUS]
        [MELTING_POINT:10000]
    [SELECT_CASTE:ALL]
        [DIURNAL]
    [APPLY_CREATURE_VARIATION:CRASH]
    [APPLY_CURRENT_CREATURE_VARIATION]

And it did not break DF. Added Diurnal to the list of removed tags, and again it exploded. Removed the curiousbeast entries, and DF survived.

That the curiousbeast entires are still somehow problematic is really bizarre.

Edit2:
Enabling the Curiousbeast and Diurnal entries are enough to blow up DF in the main ZAPALLTAGS cv. Enabling just two of them and Diurnal is enough for a shorter CRASH cv.

Again the interesting point being that creature is not a curiousbeast. Thus there's NOT multiple things actually being removed. On that note Description looking like a culprit for crashes was purely due to it being directly above the cv in early testing.

I think that's all I can do on this end. Hopefully this has helped shed some light on this and the related issue.

Add Note

Note

Issue History

Date Modified Username Field Change
2014-08-06 05:14 EldrickWT New Issue
2014-08-06 06:14 user1294 Relationship added related to 0006267
2014-08-06 07:29 EldrickWT Note Added: 0028442
2014-08-06 07:39 EldrickWT Note Edited: 0028442
2014-08-06 07:49 EldrickWT Note Edited: 0028442