Quote from Suicidal Insanity
Yay ASDF ! That is the error for no MPQ access.
Like I said, most of the reported things aren't issues at all, just a difference that I noticed.
Quote from Suicidal Insanity
Ah, lines are probably 0 based in error messages, will fix
Quote from Suicidal Insanity
I don't think this is an issue, if there is a reason to worry about it let me know.
Quote from Suicidal Insanity
All text matching is case insensitive, that includes unit / location names etc. They are whitespace sensitive though, although "not set" is the only param that included whitespaces. (Obviously many trigger/condition actions do)
Quote from Suicidal Insanity
Will check that - newline, tab, etc should be \n \t etc as before. E: <- Trigedit always only had special handling for newline and tab, all other chars between [1 and 31[ were converted to hex. Not sure what you mean.
Quote from Suicidal Insanity
Ya that was one of the improvements I made. Also block comments should work using /* ... */ - but I needa test those a bit more.
Quote from Suicidal Insanity
Will update if I repro this before falling into bed <- That appears to always have been a bug in text trigedit, at least I tried a 1 year old version. I'm undecided if that error should stop compilation or just add the text to the string without converting. In your specific example, it is converting the hex code to char 0 which means terminate string.
Quote from Suicidal Insanity
It also no longer requires the closing semicolon to follow the closing paranthesis - but who would ever do that? xD
Post has been edited 4 time(s), last time on Jul 14 2019, 9:16 am by Wormer.
Some.