User:JSEVERNS/Sandbox - Revision history

JSEVERNS at 05:00, 18 March 2022

2022-03-18T05:00:42Z

← Older revision		Revision as of 00:00, 18 March 2022
Line 23:		Line 23:
	'''4. Published maps are part of a collaborative process'''		'''4. Published maps are part of a collaborative process'''

	You always retain the ~~copywrite~~ on your creations. However, when you upload a map to the mapdb, you putting down a stake in a collaborative effort, and this comes with certain obligations, chief among them a willingness to contribute to the project, ~~which is~~ providing high-quality maps to thousands of users. Other cartographers may need to update your map, correct it, or even replace it if a new one is more appropriate. By uploading your map, you are tacitly giving permission for other members of the mapping community ~~alter~~ ~~or remove your~~ ~~work~~ as ~~necessary~~. ~~Likewise, if~~ you are a mapper and would like to update or alter someone else's map, start by making a good-faith effort to reach out to them for their concurrence.		You always retain the copyright on your creations. However, when you upload a map to the mapdb, you putting down a stake in a collaborative effort, and this comes with certain obligations, chief among them a willingness to contribute constructively to the project of providing high-quality maps to thousands of users. Other cartographers may need to update your map, correct it, or even replace it if a new one is more appropriate. By uploading your map, you are tacitly giving permission for other members of the mapping community to do all these things. If you are a mapper and would like to update or alter someone else's map, start by making a good-faith effort to reach out to them for their concurrence. Remember that the overriding goal is to provide the best maps possible for users and let everything else flow from that.

	==Technical Considerations==		==Technical Considerations==

JSEVERNS at 04:53, 18 March 2022

2022-03-18T04:53:52Z

← Older revision		Revision as of 23:53, 17 March 2022
Line 21:		Line 21:
	Hard drives are not limitless, and neither is bandwidth. If your map is more than 1MB in size, consider where you can find savings. (More on this below in the Technical Considerations section.)		Hard drives are not limitless, and neither is bandwidth. If your map is more than 1MB in size, consider where you can find savings. (More on this below in the Technical Considerations section.)

			'''4. Published maps are part of a collaborative process'''

			You always retain the copywrite on your creations. However, when you upload a map to the mapdb, you putting down a stake in a collaborative effort, and this comes with certain obligations, chief among them a willingness to contribute to the project, which is providing high-quality maps to thousands of users. Other cartographers may need to update your map, correct it, or even replace it if a new one is more appropriate. By uploading your map, you are tacitly giving permission for other members of the mapping community alter or remove your work as necessary. Likewise, if you are a mapper and would like to update or alter someone else's map, start by making a good-faith effort to reach out to them for their concurrence.

	==Technical Considerations==		==Technical Considerations==

JSEVERNS at 04:41, 18 March 2022

2022-03-18T04:41:49Z

← Older revision		Revision as of 23:41, 17 March 2022
Line 9:		Line 9:
	'''1. A published map is not for you, it is for everyone else'''		'''1. A published map is not for you, it is for everyone else'''

	Who is your map for? If it is for you and you alone, then this guide is unnecessary -- create whatever your heart desires. But if you intend to publish this map in order to help the community and players in their navigation, appreciation or understanding of the game world, there are some some standards you should follow. Just as motorists have reason to expect that all stop signs will be similar, no matter what road they are on, players have the right to expect that their maps will be broadly similar.		Who is your map for? If it is for you and you alone, then this guide is unnecessary -- create whatever your heart desires. But if you intend to publish this map in order to help the community and players in their navigation, appreciation or understanding of the game world, there are some some standards you should follow. Just as motorists have reason to expect that all stop signs will be similar no matter what road they are on, players have the right to expect that their maps will be broadly similar, no matter who drafted them.

	I put this item first, because it's easy to lose sight of as creators -- a published map is a ''utility tool'' for the community and players, not just an opportunity for you to force a product or vision into the game and screens of other people. While every creator has some vision for their creation, you should not let that vision interfere with the primary purpose of a map, which is simply to orient players within the game world.		I put this item first, because it's easy to lose sight of as creators -- a published map is a ''utility tool'' for the community and players, not just an opportunity for you to force a product or vision into the game and screens of other people. While every creator has some vision for their creation, you should not let that vision interfere with the primary purpose of a map, which is simply to orient players within the game world.

			'''2. Simple is better than complex.'''

			If an element is unnecessary, then either do not include it, or minimize it or keep it off to the side where it won't bother people who don't need it. Likewise, essential elements (labels, directions, connections) should only be as complex as necessary. Avoid the temptation to use elaborate fonts that defy legibility.

			'''3. Be respectful of people's time and resources'''

			Hard drives are not limitless, and neither is bandwidth. If your map is more than 1MB in size, consider where you can find savings. (More on this below in the Technical Considerations section.)

JSEVERNS at 04:35, 18 March 2022

2022-03-18T04:35:57Z

← Older revision		Revision as of 23:35, 17 March 2022
Line 7:		Line 7:
	==General Considerations==		==General Considerations==

			'''1. A published map is not for you, it is for everyone else'''
	Go here

			Who is your map for? If it is for you and you alone, then this guide is unnecessary -- create whatever your heart desires. But if you intend to publish this map in order to help the community and players in their navigation, appreciation or understanding of the game world, there are some some standards you should follow. Just as motorists have reason to expect that all stop signs will be similar, no matter what road they are on, players have the right to expect that their maps will be broadly similar.

			I put this item first, because it's easy to lose sight of as creators -- a published map is a ''utility tool'' for the community and players, not just an opportunity for you to force a product or vision into the game and screens of other people. While every creator has some vision for their creation, you should not let that vision interfere with the primary purpose of a map, which is simply to orient players within the game world.



	==Technical Considerations==		==Technical Considerations==

JSEVERNS at 04:28, 18 March 2022

2022-03-18T04:28:04Z

@@ Line 1: / Line 1: @@
-(Working draft of "Mapping: A Best Practices Guide"
+(Working draft of "Mapping: A Best Practices Guide")
 ==Overview==
-Maps are a key aspect of any roleplaying game, and Gemstone is no different in that respect. Unlike other games, however, the only maps that exist in Gemstone are those created by its players, a time-consuming with no reward except the pleasure of creation and (if you are lucky) a small modicum of recognition. If you are reading this guide, you must feel some interest in the art of cartography, and I hope that it will provide some utility or inspiration to you, whether you are a beginner considering your very first map, or an experienced mapmaker looking to refine your maps for efficient publication on the Wiki or in the mapdb.
+Maps are a key aspect of any roleplaying game, and Gemstone is no different in that respect. Unlike other games, however, the only maps that exist in Gemstone are those created by its players. If you are reading this guide, you must feel some interest in the art of cartography, and I hope that it will provide some utility or inspiration to you, whether you are a beginner considering your very first map, or an experienced mapmaker looking to refine your products for to meet the highest expectations of users on the Wiki or in the mapdb.

JSEVERNS: Created page with "(Working draft of "Mapping: A Best Practices Guide" ==Overview== Maps are a key aspect of any roleplaying game, and Gemstone is no different in that respect. Unlike other ga..."

2022-03-17T03:53:20Z

Created page with "(Working draft of "Mapping: A Best Practices Guide" ==Overview== Maps are a key aspect of any roleplaying game, and Gemstone is no different in that respect. Unlike other ga..."

New page

(Working draft of "Mapping: A Best Practices Guide"

==Overview==

Maps are a key aspect of any roleplaying game, and Gemstone is no different in that respect. Unlike other games, however, the only maps that exist in Gemstone are those created by its players, a time-consuming with no reward except the pleasure of creation and (if you are lucky) a small modicum of recognition. If you are reading this guide, you must feel some interest in the art of cartography, and I hope that it will provide some utility or inspiration to you, whether you are a beginner considering your very first map, or an experienced mapmaker looking to refine your maps for efficient publication on the Wiki or in the mapdb.