Codename: any string. Used to differentiate a cheevo with the others.
Visible/hidden: pick one to assign visibility to the cheevo (picking hidden will make it a hidden achievement, and you have to write “hidden” in place of the locked description)
Score: the score of obtaining the cheevo.
Title: name of the cheevo
Thanks for the @Szaal. Checking through again I believe the above example that through the bug does that?
*achievement - spelt correctly, located correctly
[codename] - using underscores, not repeated
[visible/hidden] - classed visible, correctly spelt
[score] - number defined
[title] - plain text, possible cause = the word ‘visible’ in the [title], possible cause = uses apostrophe?
locked description - indented, uses hidden
unlocked description - indented, plain text
I think currently @rinari’s suggestion is that ‘visible’ is a protected word and can’t be used within the [title] of the achievement. Do you have a view on that @Szaal?
Hey @Szaal, work hotting up, sorry for the delay.
Yes there is not normal/text or a passage between the *create instructions, and the declared achievements. Good question.
I’m going to try to run through this a few times to see if the bug triggers again. As well as changing use of ‘visible’ in the string zone, I’ve removed ‘unlocked’ from the codename zone, because this protected words things could possibly apply to that too. Hopefully should be able to confirm the bug is sorted after some run throughs (though I’m not certain of the logic of the potential solution!)