Intro

TLSDZ Documentation

Effort to create The Last Stand: Dead Zone private server. Document everything we know about the game.

• DeadZone-Private-Server on GitHub ↗
• DeadZone-Documentation on GitHub ↗

Our Progress

TLSDZ uses PlayerIO backend service ↗. Our task is to design a server that mimics it.

If you follow the development instruction correctly, you should be at this screen:

What’s Next?

You can help the development of the private server directly by making a change in the code. You can also help us investigate and let others develop the server.

Our general principle is:

1. Try to reach the point that our server is currently stuck at.
2. Investigate what is wrong and figure out what changes should be made to the server to progress further.
3. Write your research or make the changes directly.
4. Repeat the process.

The general sequential flow of the game is in sequential flow. It’s a good start to see where are we currently at.

Technical Insights & Troubleshooting

During our investigation, we’ve uncovered some crucial details that are valuable for general development and troubleshooting, particularly concerning the Flash-JavaScript bridge:

• Security.allowDomain Restriction: It has been discovered that Security.allowDomain in preloader/main.as@line 82 hardcodes the allowed domain for JavaScript callbacks to a specific address, ddeadzonegame.com. If the domain where the SWF is loaded differs from this hardcoded value, the JavaScript callbacks (which are essential for communication between Flash and the web page) will not work.
• Domain Manipulation Options: The allowed domain can be influenced by setting specific Flash variables when creating the player:
  • If local is set to 1, the Flash application will utilize the domain of the core.swf file (passed in the Flash variables) for its domain checks.
• Current Workaround: As a temporary solution, using the IP address 127.0.0.1 instead of localhost seems to resolve the domain issue without requiring any modifications.