Home   Help Search Login Register  

Author Topic: Map Filename convention  (Read 1698 times)

0 Members and 1 Guest are viewing this topic.

Offline Terox

  • Former Staff
  • ****
  • Follow the Sappers!
    • zeus-community.net
Map Filename convention
« on: 26 Nov 2002, 21:13:07 »
Hi.

Most of us have been in the position as server admin or voted in admin, looking through hundreds of maps on a server in the  various island and finding difficulty locating a specific map.

Most servers that have been around for a while have some form of naming convention.

However because we all use slightly different systems, we end up downloading a map we have already got,  albeit a slightly different filename

I have started a thread on Flashpoint1985 forums (Apologies ofpec) with a simple system that I propose we take up

Heres the link

:gunman:Map Filename convention

Heres the meat of the post


Quote
Here is what I propose
Template[/b][/color]
Addon Required? Map Type (Map Player Limit) Map Name (Game Version & Map version)

Example[/b][/color]

@ ctf (32) OneRoad (1.90 v1)   .noe.pbo

Here is a breakdown on each group
------------------------------------------------------------------------------------------




@[/color]
If used this denotes that the map requires an ADDON
This if recognised internationally will stop voted in admins from loading addon maps by accident causing an auto kick of some players from the server
----------------------------------------------------------------------------------
(Map Type)[/color]
Use following abbreviations
ctf = Capture the flag
coop = Cooperative
c&h = Capture & Hold
a&d = Attack & defend
dm = deathmatch
tdm = team death match
ff = flag fight
tff = team flag fight
rts = real time strategy
misc = miscellaneous (eg SW Race, anything not covered by above abbreviations)

Apologies if i missed a map type, Im sure someone will point it out
-------------------------------------------------------------------------------------
(Map Player Limit)[/color]
Not 2-30 etc, just the limit 30
--------------------------------------------------------------------------------------
Map Name[/b][/color]
Doesnt really matter what it is, or its length
Place Sqd name here if required also
-----------------------------------------------------------
(Game Version & Map version)[/b][/color]

Game Version
Initially using the game version it was made for,

However, every time a new game patch is released, it is then changed to the latest version after testing on the newer version. This would immensley help admin staff on dedicated servers to watch over the smooth transition of maps to newer game versions

Map Version
If its in BETA, then use Beta 1.0 etc
If its out of Beta, then use v1.3 or simply dont have a map version if its the final release
-----------------------------------------------------------------------------------------
Miscellaneous Guidelines[/color]

1) Use smaller case for everything (This is to do with Linux servers), but if we all do it, then every server will have exactly the same

2) Leave a space between groups
This help to give continuity in listings, (having 1 map name without a space between Map type and player limit, places it in a different position to one with spaces)

3) Optional
This is just to help organise map listings
Any BIS Maps simply leave as they are and put (bis) infront of the filename
Important
Renaming BIS standard maps causes problems when installing game patches, if the original filename is not present, the installation is aborted. To get round this, simply create a folder within your server's "MPMissions" folder and copy the originals into it, prior to changing the mpmissions filename. Then when you do come to install a new patch, simply copy them back into the MPMissions folder temporarily

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

Reason for Group Order[/color]

1) If the @ addon is used initially, then every map that requires an addon will be grouped together, and if the convention is followed exactly, within the addons grouping, each map will be subgrouped by map type
(Addons really need to be grouped together)

2) Map type, this should preceed Player limit, if not then we will have a mix n match of maptypes and the list in the map selection screen will become disorganised
------------------------------------------------------------------------------------------


So thats the idea in full and the reasons behind it.


So what do you think!!!!!


Zeus ARMA2 server IP = 77.74.193.124 :2302
Teamspeak IP = 77.74.193.123

Skunk Monkey

  • Guest
Re:Map Filename convention
« Reply #1 on: 27 Nov 2002, 18:55:38 »
LOL

I registered to see what people had wrote here after checking the official forum, but no comments.

I hope all the server owners can get together and discuss this. Anyways here my view.

SES server map naming system

(Type)(players)(addon if needed)(map maker)(map name)

Type
C0 - Coop
TDM - Team Deathmatch
DM - Death Match
CH - Capture and hold
RC - Race (yes we have about 15 races)
CT - CTF
TFF - Tam Flag Fight

coa - coop addon


Eg
co12DC_Intervention.noe.pbo
coa18DC_Easy Path(Addons).noe.pbo

My only concern with this system is not all my maps are Linux compatable names - But I'm working on it

This system is almost identical to Vetserver Naming System, and we would be happy to join any other servers with Joint Addon-Packs and map-naming systems if it was a community-wide system - I see the bigger benifs of this.



--------------
The Skunkiest Funkiest Monkey

WWW.SUICIDESQUAD.CO.UK
10mb connected Euro OFP-R Server ;)
62.20.208.73:2302
P4-2Ghz-512 Dedicated COOP server :D

Offline Terox

  • Former Staff
  • ****
  • Follow the Sappers!
    • zeus-community.net
Re:Map Filename convention
« Reply #2 on: 28 Nov 2002, 20:04:42 »
Ok its a little difficult to picture it on a forum, but try to imagine what the following looks like ingame

Its easier to scan through a listing like this

@ c&h (10) dragonlair (version etc etc)
@ c&h (18) crazyhorse (version etc etc)
@ c&h (20) ironmaiden (version etc etc)
@ c&h (22) stealth (version etc etc)
@ ctf (30) armourgeddon (version etc etc)
@ ctf (30) decisive (version etc etc)
@ tdm (32) widelyspread (version etc etc)
a&d (12) hearstopper (version etc etc)
c&h (16) breadbasket (version etc etc)
c&h (22) deliverence (version etc etc)
c&h (22) riverdance (version etc etc)
c&h (30) long way down (version etc etc)
c&h (30) Dragonlair (version etc etc)
ctf (14) my very long map name (version etc etc)
ctf (18) just another map (version etc etc)
ctf (22) hells fury (version etc etc)
tdm (12) bloodbatth (version etc etc)
tdm (18) apocolypse (version etc etc)
tdm (24) didnt know u cared (version etc etc)
tff (16) bongo drums (version etc etc)



than it is this way

a&d_12_hearstopper (version etc etc)
c&h@_10_ dragonlair (version etc etc)
c&h_16_breadbasket (version etc etc)
c&h@_18_crazyhorse (version etc etc)
c&h@_20_ironmaiden (version etc etc)
c&h_22_deliverence (version etc etc)
c&h_22_riverdance (version etc etc)
c&h@_22_stealth (version etc etc)
c&h_30_Dragonlair (version etc etc)
c&h_30_long way down (version etc etc)
ctf_14_my very long map name (version etc etc)
ctf_18_just another map (version etc etc)
ctf_22_hells fury (version etc etc)
ctf@_30_armourgeddon (version etc etc)
ctf@_30_decisive (version etc etc)
tdm_12_bloodbatth (version etc etc)
tdm_18_apocolypse (version etc etc)
tdm_24_didnt know u cared (version etc etc)
tdm@_32_widelyspread (version etc etc)
tff_16_bongo drums (version etc etc)


or this way

10_c&h@_dragonlair (version etc etc)
12_a&d_hearstopper (version etc etc)
12_tdm_bloodbatth (version etc etc)
14_ctf_my very long map name (version etc etc)
16_c&h_breadbasket (version etc etc)
16_tff_bongo drums (version etc etc)
18_c&h@_crazyhorse (version etc etc)
18_ctf_just another map (version etc etc)
18_tdm_apocolypse (version etc etc)
20_c&h@_ironmaiden (version etc etc)
22_c&h_deliverence (version etc etc)
22_c&h_riverdance (version etc etc)
22_c&h@_stealth (version etc etc)
22_ctf_hells fury (version etc etc)
24_tdm_didnt know u cared (version etc etc)
30_c&h_Dragonlair (version etc etc)
30_c&h_long way down (version etc etc)
30_ctf@_armourgeddon (version etc etc)
30_ctf@_decisive (version etc etc)
32_tdm@_widelyspread (version etc etc)



Reference Addon marker
If its not at the very start of the filename, it will easily be missed by a voted in admin, who may just mistake it as a fancy sign that the mapmaker used and attach no significance to it. Due to the fact that the maps listed above and below may not have ab @ in them
However if all the addon maps are grouped together (The only way to use this is to precede the name with @), then even those with no common sense, ie the type of player who wouldnt have a clue how to use a forum, would even ask the question.  

What is the @ for??

It would also stop admins loading maps that have addons by accident and kicking off half the players on the server without realising it


Underscores
Now that you can compare spaces with underscores, which gives more clarity?
Bear in mind this is even more distinctive ingame

Unable to see al filename
If you hover the mouse over the filename ingame, a small temporary text box opens displaying the filename in full


Here is what it looks like on Zeus (A linux server)



apart from the @ having no space between itself and ctf, you can now see how clear and readable it is
Zeus ARMA2 server IP = 77.74.193.124 :2302
Teamspeak IP = 77.74.193.123