Tehtävien nimeäminen - Standard format for mp map filenames
Posted: Sun, 2.2.2003, 20.22
Tämä nimeämisketju on vanhentunut 10.5.2016.
viewtopic.php?f=7&t=1718
Kyllikki aloittaa tästä päivästä lähtien käyttämään kyseistä missioiden nimeämis systeemiä. Tässä linkki http://www.flashpoint1985.com/cgi-bin....t=26694
Kaikki serverille laitettavat mapit tulee olla nimetty alempana mainitun systeemin mukaan.
##########################################################
Multiplayer Map Filename Convention
##########################################################
Introduction and aims
INFORMATION ONLY THREAD
Please dont start a discussion
The following filename convention is intended for global use within the OFP Community
Its aims are
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 differences
4) To set a standard map filename for future mappers to use
##########################################################
Filename Template
Example of some filenames
co 04 kuuraparta
a&d@ 40 fdf paskamissio
ctf 24 riverdance
ctf@ 32 armourgheddon
c&h 30 one road
tdm 12 deathvalley
c&h@ 24 deliverence
c&h 24 efl malden
******** Subgroups ********
The filename has been split up into the following subgroups
MAP TYPE Player Limit MAPNAME
ctf 10 tigerland
= ctf 10 tigerland
******** MAP TYPE ********
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
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@
******** PLAYER LIMIT ********
This should simply be the maximum player limit only
not 2_22, just simply 22
******** MAP NAME ********
LEAGUE MAPS
If the map is an official league map, then the name itself should be preceded by the league tag
Example of a Euroleague tag
efl
and incorporated into the name
c&h 24 efl nogova v1
(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
******** Version ********
Existing Maps
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.
_
******** General Guidelines ********
General set up
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 "maptype or player limit" 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
ADDONS
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
LINUX
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
"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 :
Code Sample
md5sum *.pbo | sort | uniq -d --check-chars=33 | cut -f 3- -d " " | xargs -i mv \{\} dup/\{\}
Edited By Broileri on 1191851645
viewtopic.php?f=7&t=1718
Kyllikki aloittaa tästä päivästä lähtien käyttämään kyseistä missioiden nimeämis systeemiä. Tässä linkki http://www.flashpoint1985.com/cgi-bin....t=26694
Kaikki serverille laitettavat mapit tulee olla nimetty alempana mainitun systeemin mukaan.
##########################################################
Multiplayer Map Filename Convention
##########################################################
Introduction and aims
INFORMATION ONLY THREAD
Please dont start a discussion
The following filename convention is intended for global use within the OFP Community
Its aims are
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 differences
4) To set a standard map filename for future mappers to use
##########################################################
Filename Template
Example of some filenames
co 04 kuuraparta
a&d@ 40 fdf paskamissio
ctf 24 riverdance
ctf@ 32 armourgheddon
c&h 30 one road
tdm 12 deathvalley
c&h@ 24 deliverence
c&h 24 efl malden
******** Subgroups ********
The filename has been split up into the following subgroups
MAP TYPE Player Limit MAPNAME
ctf 10 tigerland
= ctf 10 tigerland
******** MAP TYPE ********
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
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@
******** PLAYER LIMIT ********
This should simply be the maximum player limit only
not 2_22, just simply 22
******** MAP NAME ********
LEAGUE MAPS
If the map is an official league map, then the name itself should be preceded by the league tag
Example of a Euroleague tag
efl
and incorporated into the name
c&h 24 efl nogova v1
(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
******** Version ********
Existing Maps
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.
_
******** General Guidelines ********
General set up
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 "maptype or player limit" 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
ADDONS
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
LINUX
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
"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 :
Code Sample
md5sum *.pbo | sort | uniq -d --check-chars=33 | cut -f 3- -d " " | xargs -i mv \{\} dup/\{\}
Edited By Broileri on 1191851645