| | 487 | |
| | 488 | == Templates == |
| | 489 | |
| | 490 | |
| | 491 | == Best Practices == |
| | 492 | * As a level designer, you are a story teller. Always tell your story in several ways, since a regular user will miss some information and yet should know what is going on. E.g. send a message that some traitors have turned their flags and now cooperate with the enemy. Make sure that the concerning spaceships are re-coloured in the radar & HUD. Let one of them fly to the player and attack. (Show, don't tell.) |
| | 493 | * Reward the player when he is doing something right and correct his mistakes early, if he is doing something wrong. |
| | 494 | * Let someone else play-test your level. Where does the player get stuck? What is too easy / too hard? |
| | 495 | * Have you discovered a missing feature? Create a new ticket on orxonox.net. |
| | 496 | |
| | 497 | == Trouble Shooting == |
| | 498 | Housten, ... |
| | 499 | * the level does not show up in the level list. This looks like an XML error. |
| | 500 | * the console shows that there is an XML error. First of all: do not trust the error's line number, as the lua scripts will modify the level files when they are loaded. |
| | 501 | * Save your file and commit it. If you are lucky, your modifications since the last commit are rather small and thus you might easily spot the error when looking at the diff. (Open the Timeline on orxonox.net and open your commit.) |
| | 502 | * Undo the last edits and save the file. If the error does not show up, commit again. Now you should be able to spot the error. |
| | 503 | * Start uncommenting parts of the level (everything you created after the SpawnPoint) and regularly check if the error is gone. If the error does not show up, you just uncommented the error. |
| | 504 | |
| | 505 | |
