HomeUser Control Panel (unavailable in archive)ForumsTutorialsArt GalleryResourcesMaps

My maps MPQ has gone retarded(er)

06-16-2003, 08:27 PM#1
XooM
OK, ive been in chat channels, talked to important ppl about this, everything and it still doesnt work right.

I edited the mdx to look for the new skin in the proper place. i add the new mdxes and blp to the mpq and load the map up in the WE. It then displays this message (twice) in yellow:

missing string: westring_trigtype_playereventcode
missing string: westring_playereventcode_leave

i dont know what it means, i ignore it, and go on into the unit editor to edit a random units model to units\fotf\bear . i try to place the unit. it comes out as... a checkered block. i have all the needed files, everything in the right place. it used to come out as a furbolg but with the normal skin (before i changed the mdx to get the skin from the proper location). now it gives me this stuff. what do i do?!?!?! (note: replacing the base unit is out of the question)
06-16-2003, 08:33 PM#2
Earth-Fury
it wont apper in the masp editor. remember: whenever you save your map in the we, it removes all imported files. importt the file , and test it ingame.
06-16-2003, 08:58 PM#3
XooM
what about the retardidity of the string errors?
06-16-2003, 10:38 PM#4
Panto
If you want your files to appear in WE or UMSWE, you must simply put them in the appropriate subdirectories within the Warcraft3\ folder.

So, for your file (bear.mdx I assume) you would create a directory in the game folder called Units\ (unless you already have one) and then create the fotf\ directory in Units\. Then, if you place bear.mdx in the Units\ directory, referring to it in WE or UMSWE as Units\fotf\bear would work perfectly.

About your string errors, by the looks of them it seems as if it's not recognizing a trigger command in WE. The only time I've gotten string errors in the past was in an early version of ChrydGod's Enhancer SLK where the unit fields weren't defined yet.

Perhaps you were using UMSWE and used one of Scio's custom triggers, and then brought it into WE? Usually that causes WE to crash, but perhaps alternatively this could happen.

A trigger or programmer god will have to answer you, I'm afraid.
06-16-2003, 11:19 PM#5
XooM
lol. since i havent done any triggers, ill just delete the default ones (since they go byebye anyways).

EDIT: GRAH! i tried that, hit test map, and it didnt work :-(