PDA

View Full Version : Please test your maps or mods properly before you release them!



monoRAIL
8th Dec 04, 9:36 PM
LordLegendz's Dune Crossing map highlights an interesting issue regarding maps that I don't think anyone has mentioned before.

When you install a map that uses new textures, those textures will show up in the mission editor when you are creating your new maps. There is no way to distinguish between what textures came with the game and what ones are from new maps (I try to name my textures carefully so it's clear that they're new - for example my decals are seperated into their own folder, and my detail maps are called sand_dunes_gravel and sand_dunes_sand).

So you can create a map using a new texture, test it in the game and everything seems fine. You can even send it to a friend and if they have the right maps then it'll seem fine on their computer. However if someone plays your map and they don't have the new textures you used then the textures won't load and the map will look rubbish!

How do you solve this?
Test your new map (or mod, or whatever you're making) on a version of Dawn of War that has no new maps installed. That's the only way to be sure that your map will work ok on everyone's computer. Be careful to keep track of what textures you use and include the new textures in the zip file when you distribute your map

Lastly, if you make new textures for a map please prefix the texture names with the name of the map, so everyone is clear they're not original Relic textures.

I suspect Relic will fix all this if they get autodownloading working for the next patch but for now it's something to be aware of. Note that this will also be an issue for mods too - be sure to test your mod on an install of DoW that has no other mods or maps installed.

I'm cross-posting this in all the mod fora as I think it's pretty important.

LordLegendZ
8th Dec 04, 11:22 PM
yes.. and i fell victim to it due to my lack of experience ( first map.. i said it in my post) thanks for da great advice though