Update Form

[edbeard]

I thought maybe we could get some uniformity to how people update their maps. This might help people know what's going on with a map. I definitely don't think it should be required, but it could make things easier for everyone.

Ideas of what to put on here and how to structure it are encouraged.

Here's basically what I do with mine currently.

Code: Select all

[bigimg]"Link to your latest image"[/bigimg]

[url="url to your previous version]v2[/url]
[url="url to your first version]v1[/url]

[size=140]What You Need To Know[/size]
1. Territories -
2. Continents -
3. Other Gameplay Features -

[size=140]Changes in this Update[/size]

1.

2.

3.

[size=140]To Do List[/size]

1.

2.

3.

[size=140]Points to Discuss[/size]

1.

2.



[yeti_c]

Remember that things change as you progress... so perhaps a slight amendement for which part of the process you are in?

i.e. you should have big & small images... and a link to the XML... And also do we not have Map Info as a requirement on the first page?

C.

[edbeard]

updated the form to include map info (which I put in every post since it doesn't take up too much space) since I forgot it apparently.


I guess I could/should put large image and small image on there.

I'm not sure about the XML since that'll come at the very end and likely people would only copy this form once and delete the parts they don't use. Copying their old posts as they go. At least that's what I do.



Are you saying there should be separate map idea, main forum and final forge forms? seems excessive to me. maybe I'm just not understanding what you meant.

[yeti_c]

Are you saying there should be separate map idea, main forum and final forge forms? seems excessive to me. maybe I'm just not understanding what you meant.

Possibly - or maybe just

a) Ideas & Foundry Form (as above)
b) FF form (As above + XML)

Or ignore - and just get people to add the XML link when they're in FF...

C.

[TaCktiX]

I use this form:

Code: Select all

Version Number

Updates

Image

To Do (if applicable)

Discussion Points

It seems to work well enough. On my original post, I keep the update notes for all versions, but change older versions into thumbnails.

[bryguy]

mine is basically

Code: Select all

Current V.13:

[bigimg][/bigimg]

[url=][b]V3 [clicky][/b][/url]

[size=140]What You Need To Know[/size]
1. Territories -
2. Continents -
3. Other Gameplay Features -

[size=140]Changes[/size]

1. 

2.

3.

[size=140]To Do List[/size]

1.

2.

3.

4.

[size=140]Points of Discussion[/size]

1.

2.

3.

4.


===================================================================================================

Previous Versions:
[url=][b]V2 [clicky][/b][/url]
[url=][b]V1 [clicky][/b][/url]

=====================================================================================================

[u]Original Post[/u]

[img][/img]

(whatever I said in original post goes here)

[cairnswk]

i simply use:

Version #

Changes

Other Info & to do stuff.

Map/s

Links

I beleive this is self explanantory enough...i don't beleive in feeding to many words to the mob, they have to be able to see the changes in the map afterall this is what they're really looking at.

[gimil]

A basic form that can used through the whole process sounds like a winner to me. If we could develop a form feilds can be left blank until the appropriate time. We can have it so that starting a new topic in ideas has a pre made form to be filled out.

Go over to sugg and bug reports, click new topic and youll see what I mean.

[DiM]

V#
Done
* [insert something that was changed in this version]

To-Do
* [insert something that will be changed in the next version]

Large
[image here]
Small
[image here]

and each update post is copy pasted in the original post

[gimil]

Making a form manditory for all updates isnt something I would support. Adding and demanding more expectation isnt something I would want to do to much of.

[TaCktiX]

Instead of a mandatory form, mandate that some note must be made of things that have changed/intend to be changed. That's VERY informative for a potential commenter, and will allow them to critique a map update more accurately (roll back this edit, that edit needs to be more pronounced, etc.). Include a suggested "form" that a beginning mapmaker can fill out if they're not sure. As I'm sure you've noticed, all the people who have posted their forms have pretty much the same idea with very few changes.

[wcaclimbing]

My form is almost always:

V##
---short comment (something along the lines of "OMG look its a new update!")---
[image]
---comment on image (known problems that shouldn't be there)---

DONE:
1.
2.
3.

TO DO:
1.
2.
3.

Discussion topics:
1.
2.
3.

---closing comment---

Let mapmakers do what they want. There are lots of variations that can be used. It should be whatever the mapmaker prefers to use.

[pepperonibread]

Instead of a mandatory form, mandate that some note must be made of things that have changed/intend to be changed. That's VERY informative for a potential commenter, and will allow them to critique a map update more accurately (roll back this edit, that edit needs to be more pronounced, etc.). Include a suggested "form" that a beginning mapmaker can fill out if they're not sure. As I'm sure you've noticed, all the people who have posted their forms have pretty much the same idea with very few changes.

A suggested form sounds good to me. If it's placed in the "How to Make a Map" thread, most new mapmakers will go with it anyway. And it'll still give us some flexibility, which is always nice.