X-Studio doesn't support commented commands - it will just convert them into text which the game editor won't let you uncomment. I'm working on improving this.Orfevs wrote: Underline isn't exactly right. The parsed X3TC commented commands end up non commented invalid commands. since x-studio defaults to X2 with no readable header.
That means all advanced array handling, string handling, menu handling, and gosub/endsub end up invalid. And in TCAN.. that's a lot.
Can you send me a few of these scripts? just put a few that have these problems in a ZIP file and send them to xstudio.development@gmail.com
you've put the X-style comment outside the XML. "(This is a comment)" only works within the string, in the quote above it's after the </t>, meaning you'd have to use XML comments "<!-- text text text -->", not X-style comments.Orfevs wrote:Nope. First off, that's a valid comment. Doesn't matter where you place the parentheses ( ) - they are comments and not read by X3TC at all.mr.bear wrote:well there are those numbers in brackets after the strings: '(52)', '(53)'Orfevs wrote:That is a comment...Code: Select all
IDS_XML_UNEXPECTED_TEXT: Unexpected text ' (52) ' was detected on line 92 of '8226-L044.xml' 0x0c94: Attachment: Appending relevant XML source code: '...v:%s</t> (52) <t id="18">¸</t>(53) <t id="19">x:%s y:%s z:%...
the error message says 'Unexpected text ' (52) ', it's trying to say "why is there 52 in brackets after your string?"
if you look at the compiler window when X-Studio loads, it'll say that it didn't load your language file, it'll have a red 'error' icon next to it.
In order to use () in your text, you need to place a backslash in front. Special character.Code: Select all
1 <!-- Comment --> 2 -- Plain old error -- 3 <t id="18">This is \(not a comment\)</t>(This is a comment)
when text files can't be read you'll get an error similar to this:Orfevs wrote: Second. I never got any error message stating the text files couldn't be read. Probably because page ids are all hidden in arrays. I had to look up the log. I swear.. every damned comment. I had to either remove them or place them within <t></t> brackets - where they still are ignored.
At least I did find a single quote that wasn't replaced with " - so it wasn't all bad.. but that should have been a warning, not an error preventing the load of the textfile..
[ external image ]
mr.bear