[Solved] My map broke after importing a DDS

[Tal'Rarity]

So yeah... what's even going on.

I would post a trigger, but that would mean posting the entire .j script.

You'll have to open it then try to save It yourself.

"Expected a reserved type or handle type"

"Expected a variable name"

x about 10-20 for both.

Since everything is disabled and I am still getting errors upon saving... It definitely isn't syntax.

EDIT: Oh that's funny, thanks Blizzard. One "real" Variable got pasted in wrongly therefore bam broke, lots of stuff to re-enable now. I didn't even think a real could disable the entire map. Consider solved for now, though it'd be nice to get an answer as to why one real breaks an entire map and not just the triggers it was used in. Blizzard isn't a fan of CnP apparently.

 

[Dr Super Good]

People need to stop calling a Damage Detection System a "DDS". This name is already used by Microsoft to represent a DirectDraw Surface (DDS file with extension .dds).

SC2 uses this format for texture assets. Importing a DDS file into WC3 will obviously not work as WC3 was designed around the BLP format which serves the same purpose but is less universal. You cannot even imply that what you mean immediately as WC3 and SC2 modding overlaps such that porting textures is a concern (I am sure there exists a BLP <-> DDS converter). For this reason one really needs to call them Damage Detection Systems.

WC3 and SC2 support copy and paste sufficiently, you just seem to lack a good understanding of JASS and made an easy to do syntax error. The only stupid part with the editor is that it forces the affected triggers to be disabled which is annoying.

 

[Tal'Rarity]

Wrong, the DDS pasted in in-correctly which some times and usually happens. I don't lack a good understanding of JASS luckily. Yeah an easy to do un-noticed syntax error which shouldn't happen if values could be CnP'd correctly. The only stupid part with the editor is that it somehow disabled every trigger and not just the affected ones which is as you said quite annoying.

I don't know how SC2 works by CNP however WC3 fails sometimes and blank spaces appear into variable types sometimes.

Thread solved.

 

[Dr Super Good]

I don't know how SC2 works by CNP however WC3 fails sometimes and blank spaces appear into variable types sometimes.

This is one of the reasons why people migrated to JNGP as vJASS allows you to declare globals as part of the script instead of having to depend on GUI globals. In SC2 GUI they made globals another scripting object with triggers and functions so they copy as well as they do.

Wrong, the DDS pasted in in-correctly which some times and usually happens.

I was emphasising the fact that DDS is ambiguous as in the industry it represents a highly popular texture format (a lot of games use it). It is very easy for importing a system to go wrong, however the syntax errors should explain why and it should not be an issue fixing (at least with pJASS compiler they do, I recall the standard WE one having a number of bugs such as throwing thousands of un-helpful errors if you forget a closing tag).