Standalone release guide: Difference between revisions

From MZXWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
robble robble robble
==Getting Started==
==Getting Started==
Download a fresh copy of the latest version of MegaZeux and extract it to a new folder.
Download a fresh copy of the latest version of MegaZeux and extract it to a new folder.
Line 10: Line 8:
These are the only files mandatory to run a MegaZeux game--all other files can be safely deleted for your standalone release.  Please note that as of MegaZeux 2.84c, several features will not correctly work from this setup, including the editor, help file, and updater.
These are the only files mandatory to run a MegaZeux game--all other files can be safely deleted for your standalone release.  Please note that as of MegaZeux 2.84c, several features will not correctly work from this setup, including the editor, help file, and updater.


  mzxrun.exe        (can be renamed or have the icon changed)
  mzxrun.exe        (this can be renamed or have the icon changed)
  core.dll          MegaZeux core library
  core.dll          MegaZeux core library
  sdl.dll          SDL library
  sdl.dll          SDL library
  config.txt        Config file (see [[#Configuration]])
  config.txt        Config file (see [[#Configuration]]).
  assets/          This entire directory is mandatory.
  assets/          Most of this directory is mandatory. For best results include the entire thing; otherwise, MZX will fail to start.
  docs/COPYING.DOC  Mandatory to fulfill GPL requirements
  docs/COPYING.DOC  Mandatory to fulfill GPL requirements


In addition to including COPYING.DOC in your release, it is recommended that you provide a link to http://digitalmzx.net/ on any other website your game is released to, as releases of GPL software such as MegaZeux must have accessible source code.
In addition to including COPYING.DOC in your release, it is recommended that you provide a link to http://digitalmzx.net/ on any other website your game is released to, as releases of GPL software such as MegaZeux must have accessible source code.
Not that it is not necessary that many of these files be the same as those that ship with MZX; the files must only exist in name.


==Configuration==
==Configuration==
Line 24: Line 24:
  startup_file      Specifies a local path from the startup path to a .MZX file.  This file is loaded automatically upon starting MegaZeux.
  startup_file      Specifies a local path from the startup path to a .MZX file.  This file is loaded automatically upon starting MegaZeux.
  startup_path      Specifies an absolute path for MZX to startup in.  May be necessary for Mac OS X due to unreliable default startup paths.
  startup_path      Specifies an absolute path for MZX to startup in.  May be necessary for Mac OS X due to unreliable default startup paths.
standalone_mode  See below.
no_titlescreen    See below.
Standalone mode disables the load world menu (L/F3), causes the counters ESCAPE_MENU, HELP_MENU, F2_MENU, LOAD_MENU, ENTER_MENU, EXIT_GAME to work on the title screen, and adds the new function counter PLAY_GAME which, when set, causes MZXRun to enter the gameplay state. When the no_titlescreen option is enabled AND standalone_mode is enabled, MZXRun will immediately enter the gameplay state on startup (completely bypassing the titlescreen). Using EXIT_GAME or the escape menu will cause MZXRun to exit entirely instead of changing to the titlescreen state.


==Using the MegaZeux built-in updater to allow users to update the game or MZX version==
See the config.txt that ships with MegaZeux 2.90+ for more information on these features.
By hosting your own updater repository on the Internet and configuring MegaZeux's updater to point to that repository, you can use the updater to quickly and effectively allow users to download updates.
{{{stub}}}

Revision as of 03:08, 13 July 2017

Getting Started

Download a fresh copy of the latest version of MegaZeux and extract it to a new folder.

Which architectures do I need to release under?

Releasing simply a copy of Windows x86 should be enough to satisfy the majority of people who will play your game. For Mac OS X users, it is recommended that you use the Universal DMG. Standalone releases for Linux platforms are not recommended, as most Linux users will be able to figure out how to use MegaZeux normally and play the standard release of your game.

Which files do I need to include?

These are the only files mandatory to run a MegaZeux game--all other files can be safely deleted for your standalone release. Please note that as of MegaZeux 2.84c, several features will not correctly work from this setup, including the editor, help file, and updater.

mzxrun.exe        (this can be renamed or have the icon changed)
core.dll          MegaZeux core library
sdl.dll           SDL library
config.txt        Config file (see #Configuration).
assets/           Most of this directory is mandatory. For best results include the entire thing; otherwise, MZX will fail to start.
docs/COPYING.DOC  Mandatory to fulfill GPL requirements

In addition to including COPYING.DOC in your release, it is recommended that you provide a link to http://digitalmzx.net/ on any other website your game is released to, as releases of GPL software such as MegaZeux must have accessible source code.

Not that it is not necessary that many of these files be the same as those that ship with MZX; the files must only exist in name.

Configuration

Your game can be further integrated into MegaZeux by the following config.txt options:

startup_file      Specifies a local path from the startup path to a .MZX file.  This file is loaded automatically upon starting MegaZeux.
startup_path      Specifies an absolute path for MZX to startup in.  May be necessary for Mac OS X due to unreliable default startup paths.
standalone_mode   See below.
no_titlescreen    See below.

Standalone mode disables the load world menu (L/F3), causes the counters ESCAPE_MENU, HELP_MENU, F2_MENU, LOAD_MENU, ENTER_MENU, EXIT_GAME to work on the title screen, and adds the new function counter PLAY_GAME which, when set, causes MZXRun to enter the gameplay state. When the no_titlescreen option is enabled AND standalone_mode is enabled, MZXRun will immediately enter the gameplay state on startup (completely bypassing the titlescreen). Using EXIT_GAME or the escape menu will cause MZXRun to exit entirely instead of changing to the titlescreen state.

See the config.txt that ships with MegaZeux 2.90+ for more information on these features.