Case study
mw-tools: reconstructing a MythWar I server
mw-tools develops a MythWar I server from scratch using the game client. The project seeks old gameplay videos or recordings to help replicate original features. Its TypeScript code targets Node 16 and includes a script that creates the client's door.dat server-list file for local play. The server currently lacks data storage, multiplayer and most game features.
- Targets
- Game
- Category
- Independent reconstruction cases
- Relationship
- Independent reconstruction project
- Sources reviewed
Requirements & limits
- Prerequisites: A copy of the MythWar I client is required; development uses version 1.0.48.35.
- Prerequisites: Node 16 and npm are listed for building and running the server.
- Limits: The server currently has no stored data or multiplayer, and most features do not work.
- License: No licence stated on the project page.
Cite
BibTeX
@misc{mw-tools-mythwar-case,
title = {{mw-tools: reconstructing a MythWar I server}},
howpublished = {\url{https://gitlab.com/wander-gr/mw-tools}},
url = {https://gitlab.com/wander-gr/mw-tools},
urldate = {2026-11-09},
note = {Awesome REA entry: \url{https://awesomerea.org/resources/mw-tools-mythwar-case/}}
}Plain text
mw-tools: reconstructing a MythWar I server. https://gitlab.com/wander-gr/mw-tools (accessed 2026-11-09). Awesome REA entry: https://awesomerea.org/resources/mw-tools-mythwar-case/
Useful? Star Awesome REA on GitHub2.4k
About this entry
The description was reviewed against primary sources.
Primary sources
More in Games
- Mystic Marathon: an arcade sound ROM disassembly · Case study
- Mystic Nights Online: reconstructing the PS2 multiplayer server · Case study
- Nebula: an anime-game server emulator · Case study
- NeoXResearch: investigating NeoX archives and Python bytecode · Case study
- NetspherePirates: an S4 League Patch 34 server emulator · Case study
- Neverness to Everness: mapping a TCP connection's records · Case study