Map versioning - Revision history

Lidaxs at 15:00, 25 August 2015

2015-08-25T15:00:21Z

← Older revision		Revision as of 15:00, 25 August 2015
Line 12:		Line 12:

	Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.		Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.

			The ratings and reviews your map has received are tied to the map as a whole. They will not be lost if you update your map version.

	==See also==		==See also==

Fizzer at 16:55, 27 January 2012

2012-01-27T16:55:03Z

← Older revision		Revision as of 16:55, 27 January 2012
Line 4:		Line 4:

	The first version of your map that goes public should always be version 1.0. If you need to change a map after it has gone public, you should follow this process:		The first version of your map that goes public should always be version 1.0. If you need to change a map after it has gone public, you should follow this process:
	* Duplicate the version into 1.1 ~~(or 2.0 if you're making major changes)~~		* Duplicate the version into 1.1
	* Make your changes to this new version		* Make your changes to this new version
	* Test the new version		* Test the new version

Fizzer: moved Map Making Versioning to Map versioning

2011-07-29T18:44:30Z

moved Map Making Versioning to Map versioning

← Older revision	Revision as of 18:44, 29 July 2011
(No difference)

Grzechooo at 15:02, 28 July 2011

2011-07-28T15:02:08Z

← Older revision		Revision as of 15:02, 28 July 2011
Line 17:		Line 17:
	* [[Map Making]]		* [[Map Making]]

	[[Category:Map Making]]		[[Category:Map Making\|Versioning]]

Grzechooo at 14:39, 28 July 2011

2011-07-28T14:39:52Z

← Older revision		Revision as of 14:39, 28 July 2011
Line 13:		Line 13:
	Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.		Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.

	=See ~~Also~~=		==See also==

	* [[Map Making]]		* [[Map Making]]

			[[Category:Map Making]]

Fizzer at 18:10, 22 July 2011

2011-07-22T18:10:49Z

← Older revision		Revision as of 18:10, 22 July 2011
Line 12:		Line 12:

	Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.		Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.

			=See Also=

			* [[Map Making]]

Fizzer: Created page with "This page covers how to manage your map, how to make modifications to public maps, and best practices on managing your maps. Once a version goes public, that version can never ..."

2011-07-22T18:10:33Z

Created page with "This page covers how to manage your map, how to make modifications to public maps, and best practices on managing your maps. Once a version goes public, that version can never ..."

New page

This page covers how to manage your map, how to make modifications to public maps, and best practices on managing your maps.

Once a version goes public, that version can never be modified again. This is important as you wouldn't want changes to a map to disrupt existing games. For example, you wouldn't want territories to magically connect or disconnect in the middle of a game!

The first version of your map that goes public should always be version 1.0. If you need to change a map after it has gone public, you should follow this process:
* Duplicate the version into 1.1 (or 2.0 if you're making major changes)
* Make your changes to this new version
* Test the new version
* Set it to public

Version 1.0 will change to Retired and 1.1 will change to public. Essentially, 1.1 will replace 1.0. New games will be created using 1.1, but games created off of 1.0 will continue to play out without being disrupted.

Although you can create as many copies of your versions as you want, it's recommended to delete ones you don't need anymore as they take up server resources.