Question about updating Forge maps in Fileshare?

Discussion in 'Halo and Forge Discussion' started by MasterWizard, Jan 10, 2008.

  1. MasterWizard

    MasterWizard Ancient
    Senior Member

    Messages:
    24
    Likes Received:
    0
    Hi, I just wanted to see what you experienced map publishers do when you want to update your map. I've only posted one map, and I'm about ready to roll out my 1.1 update version, but I'm not sure exactly what the best way is. I'm assuming that since my Bungie.net forum thread is tied to my fileshare, that if I remove the old map to upload the new version, it will break and kill my Bungie.net thread, am I right? Thats no problem really, but then what should I name the new version? If I keep the name exactly the same, and someone who already has the map downloads the new version, will it overwrite their old version? Or will it make a duplicate with 001 at the end, then they would have to go and manually delete the old version and change the name of the new version? Should I actually call the new map "Map Name v1.1"? I can't explain why, but I kinda don't like having version numbers in my map names, I'd put it in the description, but not the name. So, I know you guys have done this before, what do you think is the "best" way to do this?
     
  2. xxBRYTExx

    xxBRYTExx Ancient
    Senior Member

    Messages:
    495
    Likes Received:
    93
    i suggest you just give it a new name then in ( ) say its a remake of...
     
  3. MasterWizard

    MasterWizard Ancient
    Senior Member

    Messages:
    24
    Likes Received:
    0
    Ehh, thanks for the suggestion, but its not a remake of the map, its just an updated version with slightly changed weapon spawns, fixed bomb spawns, better starting points and respawns, and straightened walls. Plus, I like the name.
     
  4. Nutduster

    Nutduster TCOJ
    Senior Member

    Messages:
    3,475
    Likes Received:
    38
    I just remove the old share, upload the new version with the same name, and publish it with a comment explaining that it's been updated. I don't know how people with the prior version are affected- they can figure that out.
     

Share This Page