Bay 12 Games Forum

Creature will be the Boulder Saurian. It is a copy of the v0.40.06 Dragon Raws, with an Undirected Item Cloud Interaction instead of DragonFire.
C_V is an unholy amalgam of all the tokens in a modded raw directory, stripped down to base tokens with CV_REMOVE_TAG prepended.
The Directive:
   [APPLY_CREATURE_VARIATION:ZAPALLTAGS]
   [APPLY_CURRENT_CREATURE_VARIATION]
The Test Location is the main Raw/Objects folder.

Reason For Experiment: Embarked with an Entity Creature that had CuriousBeast_Item. Worried they had other similar issues. Created Creature_variation removing the suite of CuriousBeast Tokens. Instantaneous crash without errorlog on loading the save. Arena mode test of directory proved to also instantly crash. Narrowed down the cause to the 3 tokens being checked for at all with CV_REMOVE_TAG.

The Experiment.
---Placed C_V directive after CREATURE:BOULDERSAURIAN.
*No Change at all -even with the CuriousBeast_* Tokens Enabled in the C_V
*You have to have a tag before it'll even process a C_V. Can't even get it to rename a creature if it's that early. Must be /after/ a token /after/ the CREATURE: token.
---Placed C_V directive after Description in BOULDERSAURIAN.
*No crash no error. DOES_NOT_EXIST allows bizarre raws apparently. removed.
*Expected Explosion. The Curious Beast Suite is problematic. Not even an Errorlog. Initial Issue reverified. Checking Individuals
**Eater Tested
**Guzzler Tested
**Item Tested
---Removed The 3 Curious* tokens from file entirely. Enabled all other tokens in ZAPALLTAGS
*There are other deadly tokens... still no errorlog... and to reiterate this is ALL the raw tokens in the current raw folder. Even building tokens. Those are expected to crash or errorlog on check or removal.
---Disabled all changes save CV_ADD_TAGS at the bottom to give the creature a name and description.
*Trying nearly clean C_V ... perfectly fine.
*Resuming testing
**Allowing all A's... no crash no errolog
**Allowing all B's... no crash no errolog
**Allowing all C's... no crash no errolog
*Zapping "Description"... boom no errorlog

   DESCRIPTION can apparently only be overwritten? Further testing later.

**fluke check... passed?
*Resuming Testing
**Allowing all D's... no crash no errolog
**Allowing all E's... no crash no errolog
---MOVING Directive TO END... Doesn't seem to be blasting anything.
**Checking A-E's again which should obliterate parts of the critter. ERRORLOG!

   *** Error(s) found in the file "raw/objects/creature_bouldersaurian.txt"
   BOULDERSAURIAN:Tissue layer not added because no BP found: BY_CATEGORY:TOE:CLAW
   BOULDERSAURIAN Color Mod Ending With (WHITE,1) Was Not Used
   BOULDERSAURIAN Color Mod Ending With (BLACK,1) Was Not Used

*Resuming Testing
**Allowing all F's... no crash... same errorlog
**Allowing all G's... no crash... same errorlog
**Allowing all H's... no crash... same errorlog
**Allowing all I's... no crash... same errorlog
**Allowing all J's... no crash... same errorlog
**Allowing all K's... no crash... same errorlog
*Changing Test Parameters... Testing One letter at a time now. Will this be !!FUN!!?
---All Previously tested tokens disabled.
**Allowing all L's... no crash no errolog
**Allowing all M's... BOOM
---Switching to individual tag enabling
***Mannerism? Nope
***Male? ... we blasted FEMALE... no repurcussions so... ... ... assumption valid
---clearing safe tokens instead of leaving the cruft. Allows more clear view of issues... we hope.
***Material? Safe. Surprising.
***MA*?
***ME*?
***MI?
***MO?
***All but Mundane in MU
---Mundane is the 'gut feeling' suspect. Not very scientific...
***Mundane?... Houston Testing has a problem. Something in M sploded... but we've eliminated them all.
***Checking Name before we vanish back to reset part of the test land... in case I had that accidentally also selected.
*Verified. The M set if all enabled and checked for/removed will crash.
**MA? Doesn't seem to be in MA.
**ME?
**MI?
**MO?
**MU?
---Beginning double section tests.
**MA and ME? BOOM. Checking Rest of M. MI MO MU? No crash. No Errorlog
-------We apologize for the Token Hopscotch.
***All but Mannerisms. Mannerisms cleared of all charges.
***Male ...? Cleared.
***Magma*? Magma is safe. Heh
***Max? Cleared
***Metal*?
***Merc?
***Menial Work Exe*
***Meat*?
***Matunial<sp>
***MEnt?
***META... does it break?
***Meanderer?
***Megabeast? Cleared of all charges... leaving mostly material science.
---Suspicions are on Meltingpoint in this Token Hopscotch.
***Meltingpoint? Are you our MA's and ME's culprit? CULPRIT FOUND
****Meltingpoint combined with other MA tokens kills DF. Time to find which ones.
****MatFixed? Cleared...
****Suspicions in place. Clearing Chaff Slowly... MATERIAL_VALUE should be safe. It is.
****MATERIAL_REACTION_PRODUCT. Safe
****MATERIAL_PLACEHOLDER? Safe
****MATERIAL_FORCE_MULTIPLIER? Safe
****MATERIAL_SIZE? Safe
---Only 3 left counting our Culprit
****MATERIAL_TEMPLATE? Culprit Discovered.
****Material? Culprit.

   [CV_REMOVE_TAG:MATERIAL]
   [CV_REMOVE_TAG:MATERIAL_TEMPLATE]
   [CV_REMOVE_TAG:MELTING_POINT]

****Are all bad. /As a group/.
*Resuming Testing at N. Fluke test passed.
**N?
**O?
---Warden Test. Putting everyone /left/ on report. Only an Errorlog.

   *** Error(s) found in the file "raw/objects/creature_bouldersaurian.txt"
   BOULDERSAURIAN:Attack CLAW seems to have correct format but could not find proper BPs in any caste, so not added
   BOULDERSAURIAN:Unrecognized Creature Token: MULTIPLY_VALUE
   BOULDERSAURIAN:Unrecognized Creature Token: COLDDAM_POINT
   BOULDERSAURIAN:Unrecognized Creature Token: HEATDAM_POINT
   BOULDERSAURIAN:Unrecognized Creature Token: IGNITE_POINT
   BOULDERSAURIAN:Unrecognized Creature Token: IF_EXISTS_SET_MELTING_POINT
   BOULDERSAURIAN:Unrecognized Creature Token: IF_EXISTS_SET_BOILING_POINT
   BOULDERSAURIAN:Unrecognized Creature Token: MELTING_POINT
   *** Error(s) finalizing the creature BOULDERSAURIAN
   BOULDERSAURIAN:FEMALE:upper body, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:lower body, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:neck, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:head, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:right front leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:left front leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:right front foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:left front foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:right rear leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:left rear leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:right rear foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:left rear foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:tail, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:nose, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:throat, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:first right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:second right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:third right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:fourth right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:first left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:second left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:third left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:fourth left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:first right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:second right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:third right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:fourth right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:first left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:second left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:third left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:fourth left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:mouth, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:FEMALE:tongue, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:upper body, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:lower body, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:neck, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:head, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:right front leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:left front leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:right front foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:left front foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:right rear leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:left rear leg, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:right rear foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:left rear foot, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:tail, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:nose, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:throat, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:first right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:second right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:third right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:fourth right front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:first left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:second left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:third left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:fourth left front toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:first right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:second right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:third right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:fourth right rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:first left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:second left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:third left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:fourth left rear toe, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:mouth, layer 1: Tissue SCALE was not found, using first tissue instead
   BOULDERSAURIAN:MALE:tongue, layer 1: Tissue SCALE was not found, using first tissue instead


---Presumption. All Crash Tokens found.
---One Final Test... presumably no further testing will be necessary.
*Fresh Errorlog

   *** Error(s) found in the file "raw/objects/creature_bouldersaurian.txt"
   BOULDERSAURIAN:Unrecognized Creature Token: MELTING_POINT

---Test Concluded.

General:
UNIQUE_DEMON will soft fail in the "Raw Check Phase". In world gen Ear Worms and Heralds will spill out of the Circus. These should be your only two errors using either of the main packages.
Angels:

• Angels have FLIER so pathing can break. Emergency Ramps henshin yo. KNOWN DF ISSUE
• Angels have FLIER so trade is broken. KNOWN DF ISSUE
• Marriage. They will and they do, but you might have to wait a while for them to get friendly enough. etc etc. Perhaps they are Too busy working? HINT HINT
• You might have Super Moms. This is what I call it when a married lady cranks them out every time she can, and at the upper ranges.

Foocubi:

• Foocubi will burst forth with their attacks at nigh on any provocation. Sure it's not dragonfire, and it is short duration but... not fully tested (high rate of mobility loss that's not trivial or temporary in parent civs that aren't immune... not sure if it is the Foocubi or not... you've been warned).
• Due to issues with parenting outside their actual civilization, they've had eating and drinking zapped. Also they tended to prefer external water sources anyway... which is a mess on some embarks.
• Pop ratio removed from the ladies. Put it back if you're so inclined. Of course I've also made the ladies just as trainable...
• They seem to go nuts for parent civ members who adore some aspect of their species. You have been warned.
• They have 'Den Mother' issues. This is where a male and or a female will just be ULTRA POPULAR and everyone will gravitate to them. This can happen nearly instantly... sometimes right after "Seeking Infant".
• CIV SIDE: As they are a [Pet] Civ... they might not want your orders from within game (Hi Runesmith! Hi Dwarf Therapist!), and they don't have the page right before "Thoughts". So Mandates? What mandates. Room need? What room need.
• CIV SIDE: I've not removed the [PET] tag after embark for testing purposes. It should fix a few issues (Seeing Demands/Mandates/Thoughts)
• CIV SIDE: Marriage. They will and they do, AND you might get wedding cascades...

Lolin:

• Marriage. They will and they do, but you might have to wait a while for them to get friendly enough. etc etc. Perhaps they are Too busy working? HINT HINT
• You might have Super Moms. This is what I call it when a married lady cranks them out every time she can, and at the upper ranges.

Seputus:

• They are a religious Civ. Thus they are missing 90% of the nobles... and don't need them per se. Plan accordingly.
• You might have Super Moms. This is what I call it when a married lady cranks them out every time she can, and at the upper ranges.

Fallen:

• They are a religious Civ. Thus they are missing 90% of the nobles... and don't need them per se. Plan accordingly.
• You might have Super Moms. This is what I call it when a married lady cranks them out every time she can, and at the upper ranges. Don't be surprised about a Human and an Elf having a Goblin kid.

Downtrodden:

• As they have pack numbers you may not want to even think of copying an entity and putting them into it. They are also pets. This has some of its own eccentricities.
• You might have Super Moms. This is what I call it when a lady cranks them out every time she can, and at the upper ranges. Don't be surprised about a Human and an Elf having a Goblin kid. ASSUMING THEY SIT STILL UNTIL THEY HATCH

Trade Mods:

• Dwarves Don't Need Diplomats -already exist- so do not add. Elves USED to have Diplomats and thus re-add the "Appointed by Druid" bit to entity_default.txt
• Guild Representatives are NOT NEEDED for the civ you're planning to play. In fact things get weird! Which list is the one the tradesmen will obey? The Outpost Liason or the Guild Representative?
• Shouldn't try to add to the Animal Peoples as they are layer linked -thus in little camps IN the ground- and likely not able to reach you in any event.

I've not tested every single thing from all the cobbled together mods.
The Mad Scientist Workshop is mostly untested.
Grand Cheeseworks is mostly untested however Delicious Succubus Cheese Thrones! Whee!
Haven't spent the time to test changes to the Mixery, or the Imaginarium.
As mentioned elsewhere the S.L.A.D.E. gems all show up fine... but then they're mostly from Wasteland...
I've added male and female and neutral bits[/] to many species, but not all of them. There are many missed intentionally or not "No yeti buttcheeks all over the place!" for example. I mostly hit creature standard, the dragons, and I made sure to hunt down the tigermen too. There are now *2* male bits... one without a grasp and one with. Some species still have a grasp. just look for those body tags.
Added wings to Angels, and I think I finished adding them to Fairies and Pixies.
Derpicorns -flaming or not- have ungodly hitpoints the blasted Nurgle followers. I've not zapped them from the files. They still come out of the woodwork in droves. Remember Flaming Derps have dragonfire...
I've not modded Badgers. I want to. BADLY. But then Runesmith has the Nuke button. There's DFHack for that at the moment.
The Downtrodden have a trade capacity. It's untested. They will be used as beast of burden.
As sometimes things fall off when doing major mod work I've included my "nfo" files so you can make sure things are A-OK. Mostly the entity_*.permissions.nfo would need to be checked.
NIGHT_CREATURE_HUNTER seems to be another way to gain immediate hostility, besides UTTERANCES.
All the *breakable parts in the biggun body file will snap off with work. Yes something can kick a biggun's head off due to the DIGIT tag on the humanoid_breakable head declaration. You can also kick off the lower body... Flame Bint vs Bronze Biggun if you wanna see for yourself.

I've resisted combining half of everything into the Town in a Box. Or the EMK... AND resisted putting everything in it's own building.