• Do not use Works in Progress as a way of avoiding the releases system! Works in Progress can be used for sharing early betas and for getting suggestions for improvement. Releases of finished content are not allowed in this forum! If you would like to submit a finished addon, click here for instructions on how to do so.

The MS Reform -- Editing Information

Status
Not open for further replies.
Spazzo

Spazzo

Member
Please be sure to have read the following thread first!: http://mb.srb2.org/showthread.php?p=669090#1

For those who are intending to create EXE modifications for SRB2 in the future, please take note of some new modification options in doomdef.h that must be changed to ensure master server compatibility. For your convenience, I've pasted the relevant lines from v2.0.5's doomdef.h below:

#define CODEBASE 205 // For future use, the codebase is the version of SRB2 that the modification is based on, and should not be changed unless you have merged changes between versions of SRB2 (such as 2.0.4 to 2.0.5, etc) into your working copy. Will always resemble the versionstring, 205 = 2.0.5, 210 = 2.1, etc.

// HIGHLY IMPORTANT Modification Options, MUST be changed when creating a modification (or updating SRB2), else a lot of errors will occur when trying to access the Master Server. If you are just making clientside fixes for private use, that will not break netplay, these options are not important, but any builds not compatible with the normal SRB2 release must change these options accordingly, if they are compatible with normal releases but you would still like to enable the updating feature, you must still change these values.

#define MODID 1 // The Modification ID (1 = Official Build), must be obtained directly from Cue (http://mb.srb2.org/private.php?do=newpm&u=758), DO NOT try to set this yourself without speaking to Cue, it will cause a lot of problems and your modification will be unplayable through the Master Server.

#define MODVERSION 205 // The Modification Version, starting from 1, do not follow your version string for this, it's only for detection of the version the player is using so the MS can alert them of an update accordingly. Only set it higher, not lower, obviously.

#define UPDATE_ALERT // Comment out this line to completely disable update alerts (recommended for testing, but not for release)

#define UPDATE_ALERT_STRING "New updates are available for SRB2\nPlease visit SRB2.org to download them.\n\nYou will not be able to connect to the\nMaster Server until you have updated to\nthe latest version!\n\nCurrent Version: %s\nLatest Version: %s" // The string used in the alert that pops up in the event of an update being available. Please change to apply to your modification (we don't want everyone asking where your mod is on SRB2.org!).
Click to expand...

This block of code allows your EXE modification to receive update alerts through the Master Server, though do note that anyone who has not updated will not be able to use the Master Server at all, though it can be disabled. If you wish to disable update alerts, comment out '#define UPDATE_ALERT'. When updating your modification, please contact Cue once again and he will update the version data in the database. Please adhere to the instructions in the comments, and ensure that #MODVERSION starts from 0, not as something relative to your VERSIONSTRING such as 205 (SRB2 v2.0.5), this is kept exclusively to VERSION and SUBVERSION (not seen above).

For more information, feel free to contact Cue, Inuyasha~, or myself.
 
Last edited:
Status
Not open for further replies.

Who is viewing this thread (Total: 1, Members: 0, Guests: 1)

Back
Top