Error Codes Identification

Oh no! Did I do something worse than 404?

We all make mistakes from time to time – it's just a part of being human. Our aim is to prevent these mistakes whenever we can, which is only natural. However, when it comes to creating maps, there might be certain elements in our designs that could potentially lead to issues within the game.

It's worth mentioning that the nature of these issues can vary based on the specific Level Editor you're working with. I'll provide information about the types of errors that can occur in both editors.

Since Plazma Burst 2 runs on Flash, it would be a good idea to take a look at this error code in the Flash environment here: https://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/runtimeErrors.html

Error Code numbers once launch the map

Error CodePossible problemExamples to solution

2015

  • The map has no walls or takes too little space.

  • Players can’t even spawn in the map in DM/TDM mode.

  • Add more walls or make the arena bigger.

0/1009

  • Misspelling of models.

  • The map has more than 99 barrels, weapons, vehicles, or characters.

  • Check the spelling on every single guns/players/decorations if you are using old editor.

  • Remove some of entities to reduce the issue.

1905

  • Too many items, such as characters, weapons, vehicles, or triggers. This is not counting statics, such as walls, backgrounds, water, or lights.

  • Remove some of entities to reduce the issue.

1090

  • Similar to 1905, exclusive case for old editor.

  • Also possible in cases when symbols " or < or > used (in parameters of any object)

  • Use double ' instead of " to make your map work.

1502

  • Map takes too long to load, maximum time is at least 15 seconds.

  • This however, depends on your computer. In the event that a map takes too long to load.

  • Decrease the shadow quality with the Shadow map Size engine mark

  • Reduce the amount of lights.

  • Change a new browser.

  • Resize your map smaller.

2004

  • Wrong parameter value on background object

  • Zoom out your map in Level Editor and then select everything with selection region.

  • Then take a look at Objects list here you might see objects which are not selected. Select them with click in Object list and manually change their position and size parameter values to correct ones or simply remove these objects.

1010

  • Map load fails

  • LoadMap_StopAddress of 8 means it happened during level attachments handling or water objects construction (most probably not due to water).

  • Some object's property pointing towards non-existing object (It was renamed or removed)

  • Try to verify properties of attached objects for red "ERROR" values.

  • Update your standalone plazma burst 2 to newest version.

Error Messages in Level Editor

Error Messages/Symptom

Possible Problem

Examples to solution

GUI messages at left corner in level editor (press Q to visible)

  • Commonly seen in the Advanced Level Editor, which is usually caused by a conflicting trigger layout (not set up right),

  • Added the model that the editor does not realize (M4A1, "Green" barrel, and Glock are models that are not realized).

  • Fix the error by what the messages given.

  • After approximately 20 error messages, it will become visible without pressing Q, but only shows the 20th messages onward.

Unknown model on screen (?)

  • In the event that a model is deemed unknown, it will be a black figure.

  • Reselecting the model you chose.

Yellow Input Box

(Advanced Level Editor)

  • This will occur when typing in a quotation mark or apostrophe in the Input. An example is using the Text trigger.

  • The rest of the text will show, but the quotation mark or apostrophe(s) will not appear. This also goes for other unrecognized symbols.

Red Input Box

  • An argumentative or unknown input.

  • An example is putting in words in the X-value for a Push Zone.

  • Once red, it cannot be entered, which will prevent any argumentative actions between the input and the object.

Lot of code appears on Save

  • Connection problem happened during saving operation.

  • It is better to Save map again till this message disappear. Or else you can lose your map and appeared code will not help you to revive it back.

Local Storage failed

  • Connection or local base problem while saving maps.

  • Try to save the map again.

  • If you meet a closing application window while closing the map, cancel, copy all the parts and open a new map, save it. If it succeeds, move it back and save it again once reloading the editor.

Other Error Messages

Error Symptoms

Possible Problem

Examples to solution

Flash player plugin crashed with a dead puzzle face

  • Something unusual happends during loading or level execution, for example map requested too much RAM.

  • This can happen when there is Lamp object(s) with high value of "power" parameter

  • Reduce the power of light

    (we recommend values below 1).

  • Avoid making mod gun that exploding power is too high.

Black Screen Upon launch the map

  • Player does not exist.

  • Add players in the map.

  • Check if you accidentally added actor where supposed to be players.

Players can't swim in Water area object

  • It can happen due to negative size of Water area object.

    (ghost water on dragging in layer which is not involved water layer)

  • Recreate the Water area object or resize it.

Camera freezes when player walked in region

  • Possible cause by a trigger execution, or what causes the trigger execution. (most commonly seen in Old Level Editor)

  • Check the spelling of the ID.

Last updated