Jump to content
Sign in to follow this  
terox

Map filename convention

Recommended Posts

I will leave it running till the weekend, then this particular part of the discussion (spaces) will be closed thank god!

Share this post


Link to post
Share on other sites

The spaces argument is finally ended

System A is to be used

ctf@ 34 mymapname

Now just 1 other little problem

co

or

coop  

makes no difference to me

I think coop is a bit more obvious and self explanatory

I go with coop

Lets vote and get this sorted then i can post a beta convention template post

wow we are nearly there

Share this post


Link to post
Share on other sites

co - as most already expressed when they were voting on the space... wink.gif

Share this post


Link to post
Share on other sites

Maybe it´s time to end this so people could start working.

Share this post


Link to post
Share on other sites

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (Goeth[kyllikki] @ Jan. 21 2003,17:03)</td></tr><tr><td id="QUOTE">Maybe it´s time to end this so people could start working.<span id='postcolor'>

Yes, I think it's clear from the votes so far: 'co' is it, and the space before the number of players. I think we're finished. The '&' was to be used, right? Or do we need a seperate vote on that, too?

Share this post


Link to post
Share on other sites

I also though the "&" was agreed. At least i agree on that.

Share this post


Link to post
Share on other sites

Looks all done to me ...

Terox - time for your final summing up and hopefully a mod will close the thread - anyone not stated there opinion in last 3 months can keep it to themselves.

Share this post


Link to post
Share on other sites

Great

The co's have it

I will post the full convention this weekend for checking

As we mentioned earlier, have a look through it, make sure there is nothing open for misinterpretation, its nice and compact etc, then when its all nice and tidy etc, we will open a new thread, post the convention as the start post and any post that follows it is simply to state

X server is using the convention

X league is using the convention

I will also try to get OFPEC to post the convention somewhere suitable, and Avonlady and any other community site etc etc

Share this post


Link to post
Share on other sites

By the way has anyone got any experience with a cti (Capture the Island) type map

Does it need its own tag or is it a ctf or some other map type.

I have never played a cti, so i dont know anything about them

Share this post


Link to post
Share on other sites

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (Terox @ Jan. 23 2003,00:52)</td></tr><tr><td id="QUOTE">By the way has anyone got any experience with a cti (Capture the Island) type map

Does it need its own tag or is it a ctf or some other map type.<span id='postcolor'>

Its basically an RTS map, isn't it? You build units and bases, you have to destroy the other teams base and construction vehicle, etc. Not CTF or C&H, but real RTS. As there are other RTS maps (by Karillion), we should just put them all together and use the RTS tag.

Share this post


Link to post
Share on other sites

Ok here goes.

The following posts will be restarted in a new thread and they are for information purposes only, with any replys merely being to say XXX of YYY server supports and uses the convention

##########################################################

<span style='font-size:14pt;line-height:100%'><span style='color:red'>Multiplayer Map Filename Convention</span></span> (Thread Title)

##########################################################

Post 1

<span style='font-size:12pt;line-height:100%'><span style='color:blue'>Introduction and aims</span></span>

<span style='color:blue'>INFORMATION ONLY THREAD

Please dont start a discussion</span>

The following filename convention is intended for global use  within the OFP Community

<span style='font-size:11pt;line-height:100%'>Its aims are</span>

1) To create an easily navigable and organised map listing system

2) To be simple and informative

3) To reduce multiple downloads of the same map from various server due to a small filename difference

4) To set a standard map filename for future mappers to use

(Thanks must go to)

Itchy, Kegetys, whisperFFW06,  Lt_Damage, nierop,  benu, zinco, JRMZ,  oo7vet,  KaRRiLLioN, eisa01, Goeth[kyllikki], Shrike,  HellToupee,  MadDogX,  peanuckle_00, morteni55, [TNF]Steiner.

Special thanks goes too Skunk Monkey and joltan for their unrelenting vigilence throughout the 3 month discussion)

<span style='color:red'><span style='font-size:11pt;line-height:100%'>Important</span></span>

Please only reply to the thread to state

1)Your name

2) Who you represent

and a basic statement eg "We support and use the convention"

##########################################################

Post 2

<span style='font-size:12pt;line-height:100%'><span style='color:blue'>Filename Template</span></span>

<span style='font-size:11pt;line-height:100%'>Example of some filenames</span>

ctf 24 riverdance v1

ctf@ 32 armourgheddon beta 1.1

c&h 30 one road v2

tdm 12 deathvalley beta 1.6

c&h@ 24 deliverence v1

c&h 24 efl_malden v1

                   <span style='font-size:12pt;line-height:100%'>********  Subgroups  ********</span>

The filename has been split up into the following subgroups

<span style='color:blue'>MAP TYPE</span>  <span style='color:red'>Player Limit</span>  <span style='color:blue'>MAPNAME</span>  <span style='color:red'>VERSION</span>

<span style='font-size:11pt;line-height:100%'>    ctf         10         tigerland    v1</span>

= ctf 10 tigerland v1

                   <span style='color:blue'><span style='font-size:11pt;line-height:100%'>********  MAP TYPE  ********</span></span>

The following abbreviations are to be used

a&d   -  (Attack & defend)

co     -  (Cooperative)

ctf     -  (Capture the Flag)

c&h    -  (Capture and hold)

rc      -  (Race)

tdm   -  (Team Deathmatch)

dm     -  (Death Match)

ff       -  (Flagfight)

tff      -  (Team Flag Fight)

e&e    -  (Escape & Evasion)

rts     -  (Real Time Strategy)

misc   -  (Miscellaneous) not belonging to a map type)

@      -   DENOTES ADDON USED

<span style='color:red'>If the map uses any addons at all, in addition to the BIS standard addons that came with the various patches, the Tag "@" is to be attached to the end of the maptype abbreviation

eg   ctf@

eg   c&h@

eg   co@</span>

<span style='color:blue'>I will try to keep this updated as further map types evolve</span>

                   <span style='color:red'><span style='font-size:11pt;line-height:100%'>********  PLAYER LIMIT  ********</span></span>

This should simply be the maximum player limit only

not 2_22, just simply 22

                   <span style='color:blue'><span style='font-size:11pt;line-height:100%'>********  MAP NAME  ********</span></span>

<span style='color:blue'>LEAGUE MAPS</span>

If the map is an official league map, then the name itself should be preceded by the league tag

Example of a Euroleague tag

<span style='color:blue'>efl</span>

and incorporated into the name

<span style='color:blue'>c&h 24 efl nogova v1</span>

(DO NOT   alter the filename of official league maps,  approach the league, explain about this convention, and if they are willing to support the convention, they will release new maps with the altered names)

Map name in general

Ideally the name should not include the creators tag, a server tag or anything else that would clutter it up.

This type of information can and should be added to the briefing html file by the mapmaker

                   <span style='color:blue'><span style='font-size:11pt;line-height:100%'>********  Version  ********</span></span>

<span style='color:blue'>Existing Maps</span>

Any mapnames that already have existing version numbers, should be left in their original state, no modifications should be made to them or a version number added to them, if none exist. The only exception is of moving them to the correct location, eg the last subgroup location)

<span style='color:blue'>New Maps</span>

The following system is recommended not compulsory

Lets look at the development of a map from beta to finished version

1) Map released onto a server for first time to beta test

ctf@ 32 swampland <span style='color:red'>beta 1.00</span>

2) A few bugs removed and map uploaded again

ctf@ 32 swampland <span style='color:red'>beta 1.01</span>

3) A few more improvements

ctf@ 32 swampland <span style='color:red'>beta 1.02</span>

4) A few more improvements

ctf@ 32 swampland <span style='color:red'>beta 1.03</span>

5) Beta 1.3 is bug free and finished

so its renamed and becomes

ctf@ 32 swampland <span style='color:red'>v1.0</span>

6) A new game patch is released, with some extra weapons

the map maker upgrades his map

ctf@ 32 swampland <span style='color:red'>beta 2.00</span>

7) No bugs are evident, and it becomes a finished version

Its renamed

ctf@ 32 swampland <span style='color:red'>v2.0</span>

8) Somebody decides to hack the map and change some things

(simply add a letter or tag to the end of the version number so we know its is not of original origins)

ctf@ 32 swampland <span style='color:red'>beta 1.0 zeus</span>

or

ctf@ 32 swampland <span style='color:red'>beta 1.0(z)</span>

something to non conform to the recommended version number, to indicate it is not an original mapmaker release

<span style='color:blue'>In General</span>

1) Leave exisiting version numbers intact

2) Use beta 1.0 (To maximum of 2 decimal place) for beta maps

3) Use v1 (to 2 decimal places maximum) for a finished map version

4) For a major map version jump, increase the number before the decimal

_

_

                   <span style='color:blue'><span style='font-size:11pt;line-height:100%'>********  General Guidelines  ********</span></span>

<span style='color:blue'>General set up</span>

1)A space must exist between each subgroup

2) lower case must be used for linux compatibility

3) It is the admins responsibility to modify map names on his server

4) No deviation from the convention sub groups <span style='color:red'>"maptype or player limit"</span> should be allowed under any circumstances

5) BIS maps that are installed during game installation are required in their original format when upgrading with new patches (Deal with these how you see fit)

If you are going to rename them, then keep a backup copy in a folder for easy re-installation

6) Under no circumstances are underscores to be used

<span style='color:blue'>ADDONS</span>

As previously stated, the "@" tag is to be added to the end of the maptype subgroup to indicate that the map uses an additional addon to that of the standard BIS addons that come with the various patches.

Any addon that a server supports and is included in their server maps, should be available in a server "Map Pack" and should not have a tag added to the filename by the server admin.

If the mapmaker has added something to the "MAPNAME" subgroup, then it should be left there

<span style='color:blue'>LINUX</span>

1) lower case has been used as standard, for linux compatibility

2) Spaces If spaces in the filename are causing a problem for your md5 scripts their is a workaround for it

<span style='color:red'>(Need a link placing here)</span>

"The md5 thing": Unix uses spaces as separators for lists. Using spaces in filenames breaks many scripting possibilities as space separated lists don't work anymore.

There is a way of getting around some of those limitations by using xargs. Printing ONE script that does something with md5sum would not help much. People have to take care and not use space separated lists in their scripting and use filename globbing and find -print0 and xargs whenever possible/needed.

Here is one example :

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Code Sample </td></tr><tr><td id="CODE">

md5sum *.pbo | sort | uniq -d --check-chars=33 | cut -f 3- -d " " | xargs -i mv \{\} dup/\{\}<span id='postcolor'>

which moves duplicate maps to a folder called dup.

_

Below is a screenshot of the finished system as seen in the map selection screen</b>

************image here************

(Need to ask the admins on this server to upload a jpeg of the screenshot, so that it is always available for view)

The discussion (19 pages of it) which is now closed can be found at the following link

Filename discussion

Share this post


Link to post
Share on other sites

I need somebody to post an explanation, in its own thread about the linux md5 workaround, so that i can link to it from the above pre release post when it is posted into its own thread

I need input for the "wording" and set out of the post

There should be no disagreements about the content

hope thgis does it

Thanks for all the effort, help and advice that has brought us to this point

smile.gifsmile.gifsmile.gifsmile.gifsmile.gifsmile.gifsmile.gifsmile.gifsmile.gif

Share this post


Link to post
Share on other sites

Sounds good - the only things I see a bit problematic is dictating the map makers to use integers for finished map versions and limiting the decimals for beta maps to one. Often a small change/update does not justify raising the version number for a whole number, while a major rework of a map might do. I think most mission makers use up to 2 decimals - regardless of the map being beta or not. The 'beta' already makes it very clear that a mission is still not considered finished by its creator.

Therefore I'd change this:

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">1) Leave exisiting version numbers intact

2) Use beta 1.0 (To 1 decimal place) for beta maps

3) Use v1 (An integer) for a finished map version<span id='postcolor'>

to

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">1) Leave exisiting version numbers intact

2) Use the 'beta' prefix for the version number for beta maps

3) Do not use more than two decimals (like 'v1.25') in your version number

4) Indicate major update by raising the version number to the next FULL number (i.e. V1.53 -> V2.0)<span id='postcolor'>

Share this post


Link to post
Share on other sites

Terox: There is an underscore in your posting again (efl_). Afaik we decided against mixing of spaces and underscores. "ctf@ 32 efl_name of map" just looks plain silly with one underscore and the rest spaces.

"The md5 thing": As i pointed out unix uses spaces as separators for lists. Using spaces in filenames breaks many scripting possibilities as space separated lists don't work anymore. As Kegetys said there is a possibility getting around some of those limitations by using xargs. Printing ONE script that does something with md5sum would not help much. People have to take care and not use space separated lists anymore in their scripting and use filename globbing and find -print0 and xargs whenever possible/needed. If you want only one example take the one Kegetys provided somewhere earlier in this thread:

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Code Sample </td></tr><tr><td id="CODE">

md5sum *.pbo | sort | uniq -d --check-chars=33 | cut -f 3- -d " " | xargs -i mv \{\} dup/\{\}<span id='postcolor'>

which moves duplicate maps to a folder called dup.

Share this post


Link to post
Share on other sites

why am i in thanks to section  confused.gif i just posted something about addons which noone replied to and i get in the thanks to section??? im not running a server either, i just play. Why me in there??

Share this post


Link to post
Share on other sites

Convention amended

1) Removed underscore and added Underscore should not be used under any circumstances

2) Amended Version section to recommend up to 2 decimal places

Anybody who has voiced an opinion on the thread has been thanked, thats why your name has been added to the list

What i asked, was for somebody to post an explanation of what to do with MD5 scripting, in its own thread on the flashpoint 1985 forums, so that I could place a link to it in the linux section of the convention. Which would also allow a full discussion in its own thread on that one issue

(Although i admin a linux server, i dont know diddly about md5 scripting and didnt want to put something in the convention thread that may not have been accurate

Share this post


Link to post
Share on other sites

Thanks for your efforts, Terox!

Just finished renaming our 260 missions... The SES server will switch soon to the new filename convention.

Share this post


Link to post
Share on other sites

Terox: I still did not understand what explanation/description exactly you need regarding md5. md5sum generates a checksum for a given file, which should be equal for equal files and different for different files. So you can eg check downloaded files if they are correct by comparing your checksum with the one the author gave on his site. Or if files have been modified during a patch. Or if any 2 (or more) maps with different names are actually the same map with different names or different maps. HTH. As soon as all things are settled i will rename all my maps too.

Share this post


Link to post
Share on other sites

Ok as for md5 scripting.

I dont know anything about this at all

I dont understand it, so i am not able to explain it, all i need is somebody say to post the explanation for me and a work around solution of the problems that spaces can cause in MD5 scripting

like the following

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">

cut n paste following

-------------------------------

blah blah blah blah

end of explanation

-------------------------<span id='postcolor'>

then i can simply insert it into the "Linux" section of the convention post

Share this post


Link to post
Share on other sites

Ok I have updated the convention with an explanation that hopefully makes sense for the spaces argument in linux

The only thing that has changed is a small paragraph in the Linux section.

Trusting this is now totally agreeable, i will create a new thread over the weekend in its own right, post something on OFPEC linking too it and mail some other sites, i would greatly appreciate it if everybody who has helped with this can spread the word to the various dedicated servers league sites etc

Thanks a lot guys and well done!!!!! tounge.giftounge.gifwink.gifconfused.gifbiggrin.gifsmile.gif

Share this post


Link to post
Share on other sites

Well I think its you who deserver the thanks Terox .. and now we just got to hope that most of the OFP community will adopt this univerally agreed system.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×