Print

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

[Defensive kobra]

in every example creature RAW i have seen, some things seem to be defined directly, weras some reason seemingly have to use [SELECT_CASTE:ALL] or [SELECT_CASTE:(specific caste)] to work and i really want to know why

[Hugo_The_Dwarf]

When the CREATURE tag is defined and you're adding tags to construct a creature, it is effectively running on "SELECT_CASTE:ALL" basically in the background, But once you start to define a [CASTE] it breaks that and now you're adding tags to CREATURE:CASTE as a sub object of the CREATURE. Thus when you want to start adding things back to the creature again for it as a whole you use SELECT_CASTE:ALL stating "all these tags I will be adding if for the whole creature (aka apply to all castes)

when you use [SELECT_CASTE] it goes back to editing the before defined CASTE that was created before (IE MALE, or FEMALE) technically you could just go back up the caste definition and add the tags there, but the thing with [SELECT_CASTE] is there is a sister/brother token [SELECT_ADDITIONAL_CASTE] that lets you add another caste to the selection. Say you have a creature with 5 castes, and 3 of them share the same tokens, like say [BODY:2WING] instead of just adding that line 3 times in the definitions, you can just do SELECT_CASTE:A then SELECT_ADDITIONAL_CASTE:C, SELECT_ADDITIONAL__CASTE:D then add the above token of adding two wings and the flier tag and gaits.

[Defensive kobra]

When the CREATURE tag is defined and you're adding tags to construct a creature, it is effectively running on "SELECT_CASTE:ALL" basically in the background, But once you start to define a [CASTE] it breaks that and now you're adding tags to CREATURE:CASTE as a sub object of the CREATURE. Thus when you want to start adding things back to the creature again for it as a whole you use SELECT_CASTE:ALL stating "all these tags I will be adding if for the whole creature (aka apply to all castes)

when you use [SELECT_CASTE] it goes back to editing the before defined CASTE that was created before (IE MALE, or FEMALE) technically you could just go back up the caste definition and add the tags there, but the thing with [SELECT_CASTE] is there is a sister/brother token [SELECT_ADDITIONAL_CASTE] that lets you add another caste to the selection. Say you have a creature with 5 castes, and 3 of them share the same tokens, like say [BODY:2WING] instead of just adding that line 3 times in the definitions, you can just do SELECT_CASTE:A then SELECT_ADDITIONAL_CASTE:C, SELECT_ADDITIONAL__CASTE:D then add the above token of adding two wings and the flier tag and gaits.

okay but then why is it that many creatures just uses [SELECT_CASTE:ALL] just to define some stuff about hair colours, length and skin tone?

[Hugo_The_Dwarf]

Because they defined some castes, and need to use SELECT_CASTE:ALL so it adds those details to all of the castes.

[Defensive kobra]

okay but why is it nessesary for those things to be written after the castes are defined, would it not work just fine if they defined it before the castes?

[Hugo_The_Dwarf]

At this point it seems like you are trolling. if you started right after the castes, it'd only go into the last defined caste, so as I've said already SELECT_CASTE:ALL will then apply all tags to all castes IE the whole CREATURE.

[Defensive kobra]

yes but i still do not understand why you would want to do something that are applied to all castes after you have defined castes when that would mean writing one additional line of code in [SELECT_CASTE:ALL] and pressing tab one additional time per line of code you want to apply to all your castes, why not just leave defining castes to the end of the document and defining tissue colors and hair lengths and stuff a bit earlier? Why do they use this seemingly ineffective method? Is there some kind of reason why it is necessary to define all the tissue appearances last? Is it so that they can be found`and edited more easily? is it necessary to define tissue appearance at the very end of the creature for some technical reason? Sorry if i come of as a bit rude i just dont understand

[Roses]

yes but i still do not understand why you would want to do something that are applied to all castes after you have defined castes when that would mean writing one additional line of code in [SELECT_CASTE:ALL] and pressing tab one additional time per line of code you want to apply to all your castes, why not just leave defining castes to the end of the document and defining tissue colors and hair lengths and stuff a bit earlier? Why do they use this seemingly ineffective method? Is there some kind of reason why it is necessary to define all the tissue appearances last? Is it so that they can be found`and edited more easily? is it necessary to define tissue appearance at the very end of the creature for some technical reason? Sorry if i come of as a bit rude i just dont understand

As long as the appearance modifiers are defined after the tissues they modify, I'm fairly certain they don't need to be declared after the castes.

Also, the tabs are not necessary, there is no indentation requirements for the raws, so it really is just one extra line

[Madde]

Why do they use this seemingly ineffective method? Is there some kind of reason why it is necessary to define all the tissue appearances last? Is it so that they can be found`and edited more easily? is it necessary to define tissue appearance at the very end of the creature for some technical reason? Sorry if i come of as a bit rude i just dont understand

Adding that one extra line to the token framework that you are just going to copy-paste for hundreds of creatures is easier. This way, Toady didn't have to search for the space between body/tissue definition  tokens and the first instance of castes for every creature, he could just scroll to the end and add it in there.