The goal of this project is to have a free/open source re-implementation of SimCity 2000 that is faithful to the original as well as an enhanced version with various bugfixes and enhancements including: infinite cities, more graphical customization, more types of networks, more buildings, history tracking/replays, multiplayer support, rebalancing and more.

Documentation of the various binary file formats and of the simulation behaviour can be found at https://github.com/dfloer/SC2k-docs.

Note that this is very preliminary and subject to change.

This runs the simulation directly and handles updates to the client. Likely written in Python. This model was chosen to make future multiplayer support easier.

Contains the game engine and code for communicating with the server. Likely written in something better supported for game development, though kivy(kivent) and Panda3D are engine options.

Implementing basic functionality and parsing of game assets. Initial focus is around parsing .sc2 city files, .mif tilesets, .scn scenarios as well as all game assets, which will need to be sourced independently of this project as EA still claims copyright on them.

• pillow
• python 3.6+

• Opening and uncompressing city files.
• Saving uncompressed and compressed city files.
• Parsing the TEXT_USA files.
• Parsing SMALLMED.DAT, SPECIAL.DAT and LARGE.DAT sprite data files.
• Parsing MIFF files.

Basic, low-level functions for parsing IFF files, implemented for the quirks of the various formats SC2k has with its files. Also includes support for opening Mac formatted cities, something which the Win95 SC2k version lacks.
Considered more-or-less complete in terms of game functionality.

Functions to parse the raw, uncompressed data into a city and all it's associated pieces.
Support for parsing most of the savegame complete, but not all of it yet.

Helpful utility functions that get used all over.

Used to parse SC2k's internal image format.
Considered more-or-less complete in terms of game functionality.

Used to parse MIFF (.mif) tilesets. Considered more-or-less complete in terms of game functionality, but there could be some tilesets that it can't open out there. Testing has been limited.

• text_usa_parse.py: Extracts the contents of TEXT_USA.DAT. Currently very raw output.

  • -d/--data: the path to TEXT_USA.DAT
  • -i/--index: the path to TEXT_USA.IDX
  • -t/--text: optional path for exported text file. Omitting this will write to stdout.

• data_usa_parse.py: Extracts the contents of DATA_USA.DAT, the newspaper data files.

  • -i/--input: the path to DATA_USA.IDX and DATA_USA.DAT
  • -o/--output: path for exported text file.
  • -d/--debug: enable debug printing.
  • -j/--json: path for exported json file. Optional.

• tileset_parse.py: Extracts the contents of LARGE.DAT, SMALLMED.DAT and SPECIAL.DAT and saves them as either PNGs, or animated gifs of the colour cycling animation.

  • -i/--input: Path to the directory containing the 3 data files.
  • -o/--output: Path to the directory to save output in.
  • -p/--palette: Path to the file containing the palette to load. Note that this will likely be PAL_MSTR.BMP.
  • -w/--write-palette: Path and filename for the palette to be written to. Useful for debugging.
  • -a/--animate: Create animated gifs of each sprite, using the game's colour cycling system for basic animations. Saved in the same output folder as specificed in -o/--output.
  • -d/--dump: Most useful for debugging, dumps each raw frame for the animation. Saved in same output folder as animations are.

• miff_parse.py: Turns the contents of a .mif file into their sprites, much like tileset_parse.py does.

  • -i/--input: Path to the directory containing the 3 data files.
  • -o/--output: Path to the directory to save output in.
  • -p/--palette: Path to the file containing the palette to load.
  • -a/--animate: Create animated gifs of each sprite, using the game's colour cycling system for basic animations. Saved in the same output folder as specificed in -o/--output.

  Examples:

  There are some examples included what are mostly for my testing, but they should help explain how the libraries work at the least. They are located in Examples & Utilities and there is a readme there with more.

  Editor:

  There is a very experimental start to an editor/game engine using Panda3D in the editor branch. It's nowhere near working anywhere past poorly rendering a city and panning it. A lot more work needs to go into it, and I might move on from it.

  License:

  This project is using the AGPLv3, a copy of which is found in LICENSE.md