Kwaliti
08-31-2007, 01:49 PM
l0w_kwaliti's guide to removing Loading Screen crashes in maps
Introduction:
Many people get a crash at the near end of the Loading Screen in their maps. This tut is made for the creators to remove the crashes before releasing the map to the public. It's very simple actually.
Step 1: Analyzing the Imports
Most crashes are caused by a faulty import. First, delete all of your imports and test the map. Restore all of your imports (close and reopen map) and move to the next stepRestore all imports. Next thing we do is analyzing the imports. Remove them one-by-one, testing the map between removals. If one-by-one deleting didn't help, delete all of your imports and try to find a replacement.
Step 2: Analyzing the Object Data
Certain spells and abilities may cause crashes, so we shall first delete ALL CUSTOM DATA and then test the map. Restore all of your object data and move to the next stepWHOA! Wait a second! Make sure you have 1-2 hours of time for this step, because it requires removing abilities, spells, doodads, units and other things and testing them as well for abnormalities. Start removing units, abilities, etc. etc. testing the map between removals. When you reach to a faulty unit, ability, etc. etc. look for abnormalities and fix if needed.
Step 3: Analyzing the Trigger Data
Faulty codes might make the map to crash. We shall delete every trigger as we did before. Restore all of your triggers and test everything else once again.WHOA! Wait a second! Make sure you have 1-2 hours of time for this step, because it requires removing triggers and testing them as well for abnormalities. Start removing triggers, starting from the most complicated ones, testing the map between removals. When you stumble upon a faulty trigger, start analyzing the trigger, look for bugs and abnormalities and fix if needed.
Step 4: Analyzing everything else
Although very unlikely, there are things that may cause your map to crash besides triggers, objects and imports. Be sure to check them out.
I hope this was helpful.
l0w_kwaliti
Introduction:
Many people get a crash at the near end of the Loading Screen in their maps. This tut is made for the creators to remove the crashes before releasing the map to the public. It's very simple actually.
Step 1: Analyzing the Imports
Most crashes are caused by a faulty import. First, delete all of your imports and test the map. Restore all of your imports (close and reopen map) and move to the next stepRestore all imports. Next thing we do is analyzing the imports. Remove them one-by-one, testing the map between removals. If one-by-one deleting didn't help, delete all of your imports and try to find a replacement.
Step 2: Analyzing the Object Data
Certain spells and abilities may cause crashes, so we shall first delete ALL CUSTOM DATA and then test the map. Restore all of your object data and move to the next stepWHOA! Wait a second! Make sure you have 1-2 hours of time for this step, because it requires removing abilities, spells, doodads, units and other things and testing them as well for abnormalities. Start removing units, abilities, etc. etc. testing the map between removals. When you reach to a faulty unit, ability, etc. etc. look for abnormalities and fix if needed.
Step 3: Analyzing the Trigger Data
Faulty codes might make the map to crash. We shall delete every trigger as we did before. Restore all of your triggers and test everything else once again.WHOA! Wait a second! Make sure you have 1-2 hours of time for this step, because it requires removing triggers and testing them as well for abnormalities. Start removing triggers, starting from the most complicated ones, testing the map between removals. When you stumble upon a faulty trigger, start analyzing the trigger, look for bugs and abnormalities and fix if needed.
Step 4: Analyzing everything else
Although very unlikely, there are things that may cause your map to crash besides triggers, objects and imports. Be sure to check them out.
I hope this was helpful.
l0w_kwaliti