So,
When writing a Transformative Item, I've seen one of two things happen: either A) the writer in question uses as much code as possible alongside their descriptions of what happens when the player takes the item, and B) the writer only writes out what happens when a player takes the item, and seemingly leaves the mechanical aspects of it to whomever chooses to code the thing into the game once it's accepted.
My question is--and this goes out especially to creators or those who have coded things into TiTs already--which of the aforementioned is better for an aspiring writer to do? Does pre-coding the item make it easier for it to get accepted into the game, or does it just create more headaches for coders? Similarly, does just writing out all the ways that "X occurs to Y body when player Z takes Q item," and lthen submitting it to let someone else code the entry make it easier, or harder?
When writing a Transformative Item, I've seen one of two things happen: either A) the writer in question uses as much code as possible alongside their descriptions of what happens when the player takes the item, and B) the writer only writes out what happens when a player takes the item, and seemingly leaves the mechanical aspects of it to whomever chooses to code the thing into the game once it's accepted.
My question is--and this goes out especially to creators or those who have coded things into TiTs already--which of the aforementioned is better for an aspiring writer to do? Does pre-coding the item make it easier for it to get accepted into the game, or does it just create more headaches for coders? Similarly, does just writing out all the ways that "X occurs to Y body when player Z takes Q item," and lthen submitting it to let someone else code the entry make it easier, or harder?
