Map Renamer

[WaeV 5,049]

Oops, the folder browse dialog should not have been restricted to the desktop. I'll fix that soon.

 

The rigid renaming rules are because this started as a renamer for HaloMD maps, which follow a specific versioning format. I could make the build number optional.

 

Thanks for the feedback!

[Kavawuvi 7,026]

actually, HaloMD can support map names at up to 31 characters now, as of 1.0b26, since it no longer overwrites any map list slot, but it is join-only if it's on anything earlier. If you want to make it 31 characters instead of 13, then think about this.

Edited June 22, 2014 by 002

[NeX 1,756]

if it didn't need that build number, I would build things for MD. Having an awesome map name, and having to stick "_#" after it, just....idk it looks very tacky and would make a player less likely to download something. I understand its purpose, but still.

Edited June 22, 2014 by NeX

[Kavawuvi 7,026]

if it didn't need that build number, I would build things for MD. Having an awesome map name, and having to stick "_#" after it, just....idk it looks very tacky and would make a player less likely to download something. I understand its purpose, but still.

If we didn't have it, how would we:

• Remind users about a new update of the map. What if the latest update fixed a crash or something?
• Verify the host and client have the same version of the map. You don't want the host running version 1.5 and a client running version 0.9b.
• Download the latest version of the map when users want to download a map. If hosts are hosting old versions of the map, then those versions should still be available.
• Verify that submitted mods from the mod author are a newer version than the ones they submitted last (if they have done so).

Using a build number also allows the user to see if something's newer or older at a glance. Edited June 22, 2014 by 002

[WaeV 5,049]

Okay, for v1.3 I'm going to:

• Bump the name length limit to 31.
• Make the Build Number field optional (required for MD, of course, unless you do it manually in the New Name field).
• Fix the browse dialog for the Output Folder field.

Are MD map names allowed to have characters outside the [A-Za-z0-9] range? Stuff like spaces, underscores, and punctuation? What about unicode characters?

[NeX 1,756]

If we didn't have it, how would we:

• Remind users about a new update of the map. What if the latest update fixed a crash or something?
• Verify the host and client have the same version of the map. You don't want the host running version 1.5 and a client running version 0.9b.
• Download the latest version of the map when users want to download a map. If hosts are hosting old versions of the map, then those versions should still be available.
• Verify that submitted mods from the mod author are a newer version than the ones they submitted last (if they have done so).

Using a build number also allows the user to see if something's newer or older at a glance.

 

 

I understand its purpose, but still.

 

 

Still looks like shit

[WaeV 5,049]

1.3 released http://www.mediafire.com/download/3y8mjyxstk2xs86/HaloMapRenamer.v1.3.zip

• Fixed the browse dialog for the Output Folder field.
• Bumped the name length limit to 31 for non-MD maps.
• Made the Build Number field optional for non-MD maps.