Jump to content

terox

Member
  • Content Count

    2406
  • Joined

  • Last visited

  • Medals

Everything posted by terox

  1. terox

    Map filename convention

    So basically Whisper, the only reason is to check to see if the exact same file already exists, nothing to do with OFP itself. When i say exact same file, i mean similar map name, same map, same filesize Windows users (of which there are many more) have to do all this manually anyway The only locations where these pbo files are, is the mpmissions, so having all files named similar will show up those with similar names quite easily And, if the convention is followed to the letter, these filenames will be changed, in a lot of cases to the same filename, and in some other cases to a very similar filename that will be seen in the map selection screen anyway. I totally misunderstood what Benu's problem was, I thought using spaces instead of underscores would stop the file from being played or something as drastic as that. Longterm the filename convention would make Benu's script redundant anyway and short term, he will have to do no more work than the rest of us. In addition, there is a work around for him, which although requires a little more work, when it is set up does not need to be redone! If what i have put above is an accurate interpretation, then i dont really see the argument for including underscores. But please comment on this
  2. terox

    Map filename convention

    Lol karillion you nutcase (4 posts above) I posted about what exactrly does Benu want to do with these map filenames that requires O/S scripting (Forgive my ignorance of Linux) It seems to me that all you need to do with these pbo files is 1) Upload them 2) Delete them 3) Possibly rename them once As this is a major stumbling block at the moment, then we should concentrate only on this until it has been resolved This is my preference of what we should use to split the sub groups up 1) Spaces By far and away the clearest 2) . or .. (Thanks Karillion) 3) _ as a last resort, it just clutters everything up So lets get on with sorting this bit out Before we can sort this out, somebody needs to explain in plain english why these pbo mapfiles need to be manipulated in other ways apart from the three i have mentioned Then having ascertained that, we need some Linux experts to solve the issue. If it turms out to be a real major problem then we should look at other options For the moment lets put on hold version numbers, addon packs etc and just concentrate on this
  3. terox

    Map filename convention

    This is mainly for Benu I really do know very little about Linux systems, even though i have admin status on both Zeus systems So i dont fully understand why you need to do any scripting for map files. In plain english, what exactly are you doing with these files and why, other than uploading them to the server mp missions folder, possibly renaming them and deleting them and obviously playing them. It seems to me having read a few posts above that you want to run a script that renames all the maps using our convention instead of changing them manually. If this is the primary reason you need underscores, then i dont see it as a reason to use them. Every win server is going to have to rename their files manually, which does take time (Not that much though! As for admins having access, you only ideally want 1 or 2 admins in charge of uploading maps etc, I have found on SHOP that if all can upload them, you end up with chaos, unbalanced numbers of map types and maps that nobpody likes except the odd admin Yes Linux OFP Servers will probably become more popular once the bugs are sorted out. I am of the understanding that they are both faster and can hold more players. Yes spaces are for eye candy, but its eye candy on the Islands maps list that we are aiming for, among other things and it is distinctively better. Specifically if we are oing to have league tags or squad, author, addon tags etc within the actual mapmame subgroup, the we need to have the map name which will have underscores split from the rest of the subgroups If there isn't a solution to your problem, then we will reluctantly have to go with underscores. However if there is and we can post a small tutorial within the "Convention" template post explaining the work around so much the better
  4. terox

    Map filename convention

    ?? Spaces in mapfile names for linux </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">ASK about linux if you don't know instead of assuming something which just is not true.<span id='postcolor'> It has been asked </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE"></span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote (benu @ Dec. 02 2002,02:33)</td></tr><tr><td id="QUOTE">Actually, spaces DO make problems with linux, not while running the server but with using mapnames in shell scripts.<span id='postcolor'> Its your shell script that needs fixing if it cant handle filenames that the filesystem can.<span id='postcolor'> OFP does not have problems loading map files with spaces in them (or at least the only Linux system i have access too doesn't) I also said that the topic wasnt closed so dont get yer hair off %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% <span style='color:red'><span style='font-size:11pt;line-height:100%'>Linux Compatibility</span></span> Ok firstly lets find out what else you want to do with ofp map files then the more advanced linux users out there can help to solve the problems however if its to do with sorting them deleting them etc because the maps will be in an organised order, is it not easy to do these things manually??
  5. terox

    Map filename convention

    <span style='color:red'><span style='font-size:10pt;line-height:100%'>Addons</span></span> @ is the marker that denotes an addon is required That addon can be any addon. Its impossible to create a universally acknowledged coding system to encompass the hundreds of addons out there and the thousands of combinations possible for addon packs Every server that has maps that use addons should have their addons available for download If a server has maps specifically made for them and they have some internal coding system for whatever addon pack is required, then the best place to put this coding system is in the mapname subgroup itself The mapname subgroup is the only truly flexible part of the filename convention the @ sign would still be used, as would whatever version convention we use So lets play make believe A server called DZ uses an addon  pack called Nam2.0 their mapname is called Sunrise and its a 30 player ctf Filename would become ctf@ 30 dz_sunrise_nam2.0 v1 or ctf@ 30 sunrise_nam2.0 or ctf@ 30 sunrise_dz_nam2.0 The convention itself has not been changed The actual flexibility of the subgroup "mapname" gives scope for anything other than 1) maptype 2) is an addon required? 3) player limit 4) version The important thing here is, that we know it uses addons, because of the @
  6. terox

    Map filename convention

    When a couple of minor disagreements have been sorted out, and the version system agreed on, i will submit a "convention post" Which will include a detailed explanation, a screenshot example etc We will then need to edit the post so that its easily understandable and covering any questions that can be foreseen (Most of which i would imagine have already been discussed )
  7. terox

    Map filename convention

    <span style='color:red'><span style='font-size:12pt;line-height:100%'>SUMMARY OF COMMENTS SO FAR</span></span> <span style='color:blue'><span style='font-size:10pt;line-height:100%'>If you dont want to read every post start here[/b]</span></span> Lets not lose site of why this thread was started 1) Basically its to have a Universally agreed map naming convention throughout the OFP Community Impossible for every last one of us, but defintely possible among the more active servers, leagues, squads etc 2) Its to prevent those folks who jump from one server to another downloading the same map just because the filename is slightly different and to stop servers holding 2 of the same maps for the same reason 3) It has to be informative without being complicated 4) Its to organise maps on the servers in such a way, that finding a specific map doesnt involve looking at every map listed 4) It is not going to be 100% perfect for all servers, probably very few in actual fact, but its going to be a standard that we all agree to comply with 5) Its about time we did it ----------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------- The server lists maps in each island alphanumerically so to aid in organisation and map search, we have split the filename into sub groups, Priority Subgroup = Map Type <span style='color:blue'>eg ctf</span> We have agreed on various 2, 3 and 4 letter abbreviations for each map type, which are all basically self explanatory to any regular players of OFP (Topic Closed) Addon Marker <span style='color:blue'>eg @</span> We have agreed that a map that requires anything other than the standard BIS installation or gamepatches needs to be identified We have agreed that the best location for this is after the map type. (This helps to group addon maps together) <span style='color:blue'>eg ctf@</span> We have also agreed on @ as the marker (Linux users see O/S Compatibility section) (Topic Closed) Player Limit <span style='color:blue'>eg 32</span> This is the next most important marker and simply states the maximum number of players that the map caters for Earlier conventions used have been 2_24. We have agreed that the minimum number is not necessary, so we have opted for the maximum number and it is to be displayed using two digits If under 10 <span style='color:blue'>eg 07</span> (Topic Closed) Map Name <span style='color:blue'>eg efl_everonIII</span> <span style='color:blue'>eg =ca=_monolith</span> <span style='color:blue'>eg dragonslair</span> This is the group that allows for some flexibility If it is going to be tagged with a league, squad or the mapmakers tag (All of which are optional) then these tags need to preceed the actual mapname The tag and name should use an underscore, to split the two sections up whilst keeping the name as one subgroup (Topic Closed) Version Number <span style='color:blue'>eg beta1.0</span> <span style='color:blue'>eg beta1.2</span> <span style='color:blue'>eg v1</span> <span style='color:blue'>eg v2</span> This topic is the point we are generally at now There is a general consensus that every map should have a version number Initially proposed was a version number that stated the gameversion as well as the map version <span style='color:blue'>eg 1.90beta1.0</span> This idea has now been discarded There is also an argument to differentiate between Beta maps that are under test and finished maps, hence the "beta" and "v" So the proposed system at the moment is examples = ctf@ 24 efl_sundance beta1.0 after a few bug fixes becomes = ctf@ 24 efl_sundance beta1.1 and a few more fixes = ctf@ 24 efl_sundance beta1.2 all bugs fixed and released for gameversion*.** = ctf@ 24 efl_sundance v1 New game version released with some new weapons and the map has been redited to utilise the new equipment = ctf@ 24 efl_sundance v2 For maps that already exist out there without version numbers, then it is proposed to give them a default version of "v1" This is to avoid errors and confusion O/S Compatibility For linux compatibility, it has been established that everything needs to be in lower-case (Topic Closed) Also for Linux Spaces instead of underscores Spaces create a much neater and easier to read maplist They help to differentiate between subgroups They do not cause any problems to Linux o/s. The o/s filesystem does not see any difference between the following examples ctf@ 32 mymapname v1 & ctf@32mymapnamev1 It sees both files as the same file, so i can only assume from this, that it ignores spaces There does however seem to be an issue with some user scripting (Am not experienced on Linux to understand this) However this would appear on the surface to be easily remedied by some improved scripting Spaces are definitely a better visual way to split the sub groups up, see the screenshots on a previous post for a comparison (Topic still open, was closed once and agreed standard was spaces) Also for Linux @ I have testeded this on Zeus, a linux server and it caused no problems, nor did it on SHOP a windows o/s Its an easily recognised symbol and seems to be acceptible on a whole, apart from a few that seems to be having problems with scripting Some comment has been made about issues caused by downloading the file in a web browser If  there really is a problem, Simple answer, keep the filename, zip it up and use a slightly different zip filename, Makes downloading easier too (Topic still open)
  8. terox

    Map filename convention

    <span style='font-size:12pt;line-height:100%'><span style='color:red'>Summary of agreed system so far</span></span> <span style='color:blue'>maptype</span> Â <span style='color:red'>addon marker</span> Â Â <span style='color:blue'>player limit</span> Â <span style='color:red'>league tag & mapname</span> Â <span style='color:blue'>version</span> All in lower case all subgroups split by spaces No brackets ie (24) (V1) examples ctf@ 24 efl_everonIII version c&h 30 deliverance version Yes it seems we are eventually getting somwhere now ------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------ Quick question should addon tag be seperated by spaces or simply attached to end of maptype tag ctf@ or ctf @ -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- So we few that have discussed this so far, now only have to agree on the map version system Version Number If everybody is against a game version being incorporated into the mission version then so be it But we definitely have to use a map version The simplest and most descriptive would be (Beta*.*) for anything in Beta (not B, this could be mistaken by some as version B etc) and V* for anything thats classed as a finished version * would be 1.1 1 2.3 2 etc Basically whatver the mapmaker has classed for his version We also have to instigate a default version number for anything that alreadt exists that doesnt have a version number. The obvious choice is V1 This means that all the maps we have on our servers that do not have version numbers will now become Example ctf 30 mapname v1 Then if anybody wanted to change the map, de pbo and re edit it, they already have a starting post for the version number. If we use a version number, then EVERY MAP should have it incorporated Ok there will be slight problems on a few map that are similar but not the same from one server to another. (This was never going to be 100 % perfect) Having Beta stated. This basically helps admins and mapmakers to debug the map Loading a beta map up, initially helps discover bugs etc What we want to try and deter is players mailing admins on their server a Beta map that they played on another server Or voted in admins loading maps up that may crash a server. Although it isnt foolproof, some form of prewarning is better than no warning at all. It also helps the admin to prewarn the players , stating something like We are about to load a beta map, please take note of any bugs you see and if you want to comment on the map, the mapmaker is here now, or simply email him at etc etc etc. Just a nice helpful way to aid mapmakers, who without, OFP wouldnt exist Linux Compatibility I dont know much about linux, even though i have admin status on one linux server So could somebody who is knowledgeable please confirm or deny &........causes problems on Linux systems!!!!! Is this true by default or a problem with the setup which can easily be fixed? @........causes problems on Linux systems!!!!! Is this true by default or a problem with the setup which can easily be fixed? I can only comment on Zeus, there is no issues with these symbols <span style='font-size:12pt;line-height:100%'><span style='color:red'>Need to think about what to do once system has been agreed on</span></span> (The thread isnt just about filenames on servers, its also a convention for would be map makers to use it as well) After we have all agreed on a system, the we need to spread the word Things that would help 1) A spot on this website explaining the system 2) Same thing on OFPEC, somewhere prominent where it will be noticed 3) Mass emails to all websites members 4) Contact all Leagues, squads and related websites 5) A spot on every website with either a link or a "copied post" from this site, to avoid any deviation from the agreed convention 6) A list on the "Agreed Convention" post of what league, squad, server etc has taken up the system (I know this is a large task, but the more it is advertised the more chance there is for a universally used system) Convention to be in place somewhere between Dec 25th and Jan 1st
  9. terox

    Map filename convention

    1) spaces do not cause problems in linux, infact i tried changing one filename by just creating spaces, when i tried to get the os to accept the filename, it said file already exists, so i must assume linux simply ignores the spaces anyway when looking at the filename 2) (30) to 30 no real problem there, just thought it looked neater Version number You said the map maker could do this in the description ext. I didnt know this was possible (Paste a code snippet please). However that doesnt make any difference, what about the hundreds of maps out there already. would we have ctf planefrenzy listed 3 times on the server All having diferent filesizes but no idea which has machine gun emplacements and AA without loading the map Its a lot easier to have a version system in the filename than in the coding itself. Its easier for the map maker and easier for admins to control the different versions of maps For instance if there is more than one version of the map on the server (distinguished by different filesizes) how do you know which is which without loading, especially on a server with 500+ maps. Its much easier to see which is which  if it has a version number system in the filename. As for the system My initial idea was to upgrade the game version part of the filename as each map was tested on the newer gamepatch. Although this does cause admins work, it does benefit the server itself by quickly differentiating those maps that have been tested from those that havent. At the end of the day it doesnt take that long to update a few maps that the admin has just played during his session (Be honest you arent going to admin for 16 hours and then update 30 maps are ya) You are more likely to do a 3 or 4 hour stint and want a break anyway. however what was pointed out was that every player would then have to dl the new map, unless they too changed the filenames themselves which isnt practical Lets just make sure for a second we are on same wavelength. When i say rename So i then proposed to keep the game version unless the map itself was updated with new weapons etc, which is practically far easier Reason for game version Firstly dont think of it as a seperate element from the map version, its all part of a version number. Stating the game version simply makes it more obvious to differentiate between map versions and gives the admin a hell of a lot more information about a map For instance ctf 30 armourgeddon (1.85 v1) ctf 30 armourgeddon (1.85 v1.1) ctf 30 armourgeddon (1.90 v2) is far more informative than ctf 30 armourgeddon (v1) ctf 30 armourgeddon (v1.1) ctf 30 armourgeddon (v1.2) as you can see if we dont specifically place something in there to show the difference, this could and probably will happen Especially now 1.85 clients can play on 1.9 and 1.85 maps can be played on a 1.9 server. Who knows whats going to happen with 2.0 From the gameversion tag we can tell 1) The rough age of the map 2) what weapons / vehicles we could and couldnt expect to see 3) if a more up to date version of a map exists Not every server just has 1 admin in charge of uploading and sorting maps out, so with 4 or 5 admins constantly loading up maps it helps to sort things out a bit, and straight away an admin would notice a well known map that had a different game version on Imagine being on server version 2.2, and seeing a map on the selection list of a server with over 900 maps the gameversion tag (1.75v1) Look at the comparison screen shot jpegs above spaces between sub groups really make the list far easier to read, closing these gaps makes it more difficult to read as your eyes have more difficulty focussing on a specific group You only have to look at the jpg's to see this, is it not that obvious to you
  10. terox

    Map filename convention

    We havent actually had a discussion about the abbreviations for the map types yet. As it isnt greatly important as to what it is. What we have to think about is a very simple system that is easily recogniseable to anybody that plays ofp. Also allowing for future delelopments of different map types Everything is basically obvious except Cooperatives various systems used so far is co coop theres probably more as well I think Coop is by far the most obvious so the list would be a&d...........= attack & defend c&h...........= capture & hold coop.........= cooperative ctf............= capure the flag d&d...........= defend & destroy tff.............= team flag fight ff..............= flagfight tdm...........= team deathmatch dm............= deathmatch rac............= race misc...........= miscellaneous (anything not covered by above) If there is a major group that I have missed out that needs inclusion let me know As for c&h, a&d and d&d there are differences between these types of maps "rac" there is at least one server that i know of that has quite a few race maps, which is why i have included it in the map types So hopefully there will be minimal disagreements on this aspect. If that is the case, we only need to agree now on 1) spaces v underscores 2) version system We also need to get every league to join in this discussion and all the major servers  and squad servers that run 24/7 Lets also try to get a completion date on the convention for say Dec 25th and bring the new system online by Jan 1st Also, when we are nearly done, we can ask the sites admin to do a mass email to all its members (Hopefully they will be happy to do this as its for the good of the community)
  11. terox

    Map filename convention

    Underscores V spaces Both systems work in both dedicated server o/s and as yet there has been no reports of any problems using spaces on either systems. I am lucky to have server admin rights on both a linux and win system. So, it then comes down to the most visually pleasing and ease of reading. So, here are two screen shots of both systems (The filenames still have capitals etc, and different versions sytems) but that doesnt matter in this case, because this post isnt a discussion about that With Underscores With Spaces Now that you can clearly see the differences, there is no way that you can argue for underscores
  12. terox

    Map filename convention

    Totally agree skunk monkey, i have already spoken to efl league, when i get time I will mail the other leagues, however any help that anybody can give in contacting the various organisation would help Due to the fact that these leagues dont have hundreds of maps, i dont foresee a problem. EFL has already agreed to follow any convention
  13. terox

    Map filename convention

    I would imagine most Dedicated servers have their own website SHOP has created a forum specifically for map makers. The forum consists of wanted inclusions for server maps & some guidelines etc Very simply any would be mapmaker utilises the information that is provided. If we all have a similar thread, a) it would help mapmakers anyway b) it woulk aid the filename standard if a map maker wants to add his name to the filename, so be it, add it in the same place as the league tag or squad tag is heres the forum thread link for our beta maps and mapmakers. Stone-keep map makers guidelines when the filename convention has been agreed on, it will be updated And as far as different versions of the same maps are concerned. Yes thats bound to be the case for some These will probably have different version numbers already in the name. But i bet ya there are hundreds of maps that are exactly the same, but the filename is slightly different This is a cleanup operation, there are bound to be casualties By the way, it doesnt take long to go through the maps and rename the filenames. and if you dont want to do it all in one go, then do a little at a time also whats to stop you informing your regs as to what and how you are doing, then to save them the dl, they simply rename their map files in EXACTLY the same way as the convention uses
  14. terox

    Map filename convention

    As far as servers is concerned I represent Stoners House of Pancakes (Windows server) & two Zeus (Linux servers), one for addons and one for non addon maps These servers Stoners being presently the busiest server around and Zeus being the biggest capacity when it comes out of testing Will quite happily use whatever system is agreed on. so far the system that we agree on then is <span style='color:red'>map type(Addonmarker @) (Player limit) Name (Game version & Map version)</span> Ref Game version and map version I suppose if folks dont want to create a mass workload, then the game version the map was released in would suffice throughout its life Iff the map is re-edited to add new weapons after a game patch release etc, the filename (game version) would then change, is that fair enough and as for having the map makers name in the tag, i really dont see the point of this And spaces instead of underscores So to this point what do you guys think ----------------------------------------------------------- ----------------------------------------------------------- ----------------------------------------------------------- ----------------------------------------------------------- Thus far we have reached this point Point 1 First group <span style='color:red'>Map Type</span> including addon marker if required ie ctf@ (We still need to sort out exactly what abbreviations to use) I would prefer to use 3 to 4 letters for each map type Point 2 <span style='color:red'>Player limit</span>, a single number ie 30, not 2_30, and to be enclosed in brackets ie (32) Point 3 <span style='color:red'>Map Name</span> If it is a league map, then the name should be preceded by the league tag ie efl everonIII The same for squad maps, preceded by squad tag ie =ca= holywars Point 4 <span style='color:red'>Game version & Map version</span> 4A Game version This is to be the game version the map was created for and does not change just because a new game version has been released. However, if a new game version has been released, and the map edited to hold some new weapons etc, or for a new script or command, then the game version part should be renamed to the newer game version 4B Map version Beta's To indicate a map is in its testing stages, then Beta should be used instead of V. For each bug fix, the Beta number should be different Once out of testing stages, the beta is replaced with V and the version becomes V1 So this is a quick rundown on a map through beta to finished release. This is for a squads map that uses an addon From initial beta testing to finished map c&h @ (32) =ca= madland (1.85 beta1.0) c&h @ (32) =ca= madland (1.85 beta1.1) c&h @ (32) =ca= madland (1.85 beta1.2) c&h @ (32) =ca= madland (1.85 v1) then 1.9 comes out c&h @ (32) =ca= madland (1.85 v1) Map editor decides to upgrade map c&h @ (32) =ca= madland (1.90 beta1.0) and its bugfree c&h @ (32) =ca= madland (1.85 v1) 5 General Guidelines Spaces rather than underscores 6 ctf @ instead of ctf@ ----------------------------------------------------------- ----------------------------------------------------------- ----------------------------------------------------------- Lets quickly reply to this using the following simple method 1) Yes, Yes but, or No 2) Yes, Yes but, or No 3) Yes, Yes but, or No 4A) Yes, Yes but, or No 4B)Yes, Yes but, or No 5) Yes, Yes but, or No 6) Yes, Yes but, or No ----------------------------------------------------------- -----------------------------------------------------------
  15. terox

    Map filename convention

    Removed post was just letting off steam :-)
  16. terox

    Map filename convention

    Bearing in mind that the convention is for global use throughout the OFP Mplayer community There is no rush to implement it tomorrow, so a prolonged discussion exploring alll avenues is worthwhile <span style='color:red'><span style='font-size:12pt;line-height:100%'>THE ADDON MARKER @</span></span> This applies to servers of three types 1) Servers that do not use any addons 2) Servers that use addons only 3) Servers that use a mix of non addon & addon maps When i talk about addons, i mean ANYTHING thats is required to play a map other than the standard files installed during the game installation 1) Servers that dont use any addon, will never have the @ sign, so apart from it being a Danger marker for the server if somebody inadvertently mails it to an admin for upload, they will never see it 2) Addon servers, they will  have all map names with @ in the name, so to them, it makes no difference whether you use it in any of the following ways @ ctf ctf@ ctf @ Because which ever way you use it, the list will still be sorted in Map Type order (This is a fact) 2) Mixed map servers This is the problem one Ok lets play make believe. The admin wants to load a ctf that uses an addon For arguments sake lets say the island is Nogova, there are 100 non addon maps and 100 addon maps For each supergroup there are 25 C&H 25 CTF 25 Coop 25 Other types (Misc) So by placing the @ at the start of the filename (@ CTF) it creates 2 supergroups of 100 maps each. He knows its a ctf (Which he will know in real life) and he knows it has an addon So He goes to the first group of CTF's and searches through 25 maps.  However By placing the @ after the map group CTF@ he only has to go to one ctf map group, but he now has to scroll through 50 ctf's The CTF@ will be all listed together at the latter half of the CTF list Either way it makes no difference as to the speed of finding a map or distinguishing it as an addon The only difference is If you want to specifically load an addon map, your addon choice of all map types is together and not spread apart And vice versa for non addon maps It also makes the list easier on the eye. I have no problem with 1) @ ctf 2) ctf@ 3) ctf @ But i do think they belong together, not in the map name or after the player limit. Placing them further into the list, would cause non distinguishable sorting So what should we do I still prefer the @ preceding map type, but am quite happy to go with the flow ---------------------------------------------------------- <span style='color:red'><span style='font-size:12pt;line-height:100%'>Map makers tag</span></span> Absolutely not required in the filename How many of us use the map makers name to choose maps?By adding their tags it just adds another grouping which isnt required Mapmakers have more security placing their names ingame, where it can only be hacked by de-pbo. There are plenty of places to put it Intro Briefing etc If they really wanted too, they could place their name tag at the start of the actual map name say @ctf (30) terox-riverdance Having created map myself, i see no reason to put my name in the file name, most players will never see it, but they will see what i placed in the briefing, intro etc League maps are a different matter, they can simply preceed the actual name ie ctf (22) efl everonIII efl being Euro Flashpoint League. I did think of having league maps start with the league tag, but there are too many leagues to make this a nice neat system. ------------------------------------------------------------------------------- <span style='color:red'><span style='font-size:12pt;line-height:100%'>Game & Map version</span></span> Most admins whho just log into the server and run the server wont really understand the reasons for this, however if you have total control of a server this becomes more important ctf (30) armourgeddon (1.85 Beta 1.0).noe.pbo ctf (30) armourgeddon (1.85 Beta 1.1).noe.pbo ctf (30) armourgeddon (1.85 Beta 1.2).noe.pbo ctf (30) armourgeddon (1.85 Beta 1.3).noe.pbo ctf (30) armourgeddon (1.85 v1).noe.pbo ctf (30) armourgeddon (1.90 v1).noe.pbo ctf (30) armourgeddon (1.90 v2).noe.pbo Initially the map had its first beta release on whatever server it was tested on, which was running 1.85 It had a few bugs, so a new version was released.(Beta 1.1) This seemed to run well, so the admin deleted the older version A few more bug fixes later another version was released.(Beta 1.2) This crashed the server, so it was deleted, but the version before it was still okay (Had the filename being the same. we would have lost the previous version) Another version was released (Beta 1.3) This worked fine, no more bugs, it was taken out of Beta and the admin simply renamed the filename, swapping Beta 1.3 to v1 (v1 being the first finished map release) Now a new game patch was released (1.90) No maps had been played on the new game version, so they all remained 1.85 A few hours later 6 out of 12 maps had been played and tested, the admin having done this, then renamed the filenames, swapping 1.85 to 1.90. He then leaves the server Half an hour later another admin logs in, sees the 1.9 tags on some maps but not on others, he plays for a few hours and hey presto, all the 12 maps have now been tested on the new game version and their filenames upgraded. The new gamepatch has also brought out additional weapons. These weapons are now added to the ammo crates and map version 2 is released Joe bloggs has been playing on server A (1.9) server Map ctf (30) mymap (1.85 v1) The first time the map has been run He then goes to server B, theyve updated their mymap to 1.90 he goes back to server A to play, they have now updated mymap to 1.90, he doesnt have to dl it. But both server managed to test and upgrade the map, and there is only one version of the map on either server
  17. terox

    Map filename convention

    Ok fair enough on the addons marker being joined to the map type ie ctf@ I will amend the initial post as far as using _ between things, why on earth do you want to clutter the name up when its FAR more easier to read with spaces. I again refer to the jpeg screen shot Zeus, our 48 player linux test server has no problems with spaces, and Stoners House of pancakes 30 player server finds spaces much easier on the eye
  18. terox

    Map filename convention

    </span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">My main point was not that everybody should have editorUpdate & editorUpgrade, but that 90% of missions use them (at least, this is what happens on our server). this make the addons tag really less usefull then. <span id='postcolor'> I would agree with you, that on your server it wouldnt be as useful. However the convention is not designed for any particular server, it is designed for the whole OFP community (Which is going to take some time to fully implement) To some servers it isnt important to distinguish addon maps from others. For some servers that are only coop servers, its more important to have player limits as the primary listings Some servers only do Addon maps Some servers dont do any addons at all I spent a long time looking at all the various aspects and possibilities before i posted the convention The convention was designed to be Global, not server specific For instance Vets coop server would probably prefer to list their maps by player limit. Lets call the file 24_coop_last stand Whereas stoners would prefer to list it by map group coop_24_last stand to a 10 player limit server, the number of players isnt important at all. To combine all this into 1 filename, so that you dont download the map 3 times as you visit each server in turn I came up with the universal convention. Some aspects of the convention will be useless to some servers but very important to others Which is why I am asking you to think beyond your regular server
  19. terox

    Map filename convention

    You miss the point about the @ at the start, it isnt so that someone can ask everybody if they have the addon. Its so that the admin stops and thinks "Ah this map uses an addon, should i be loading it, shall i warn folks that i am about to load an addon map etc"!!! , so that if they get kicked, they know the reason why (Dont forget, there is no message that says to the client "You didnt have the addon******", they simply find themselves disconnected In addition Its so every map that uses addons on the server are grouped together, in much the same way as ctf's and c&h's are grouped together. For each island it basically creates two distinctive "Supergroups", 1) Addon maps 2) Non addon maps and then within these supergroups it then subcategorises them by map type (Which is why the spaces are required) It then lists those map types by player limits This makes there presence when looking through the map listings more defined and more searchable. Dont think "Your regular server", think more globally. to the extent (And this is a dream at the moment), that when u log in as say voted admin on any server all the map choices are in the same order. and split into categories in the same way. Now by not creating an addon category are you saying that Addons are not an important category and therefore it isnt really important to distinguish them from non addon maps, so this is why you want to place the addon marker, whatever it is, further into the name system, where it isnt as noticeable. You really have to forget about how it would work on your particular server and think about how it would work on every server and also think about players who dont understand diddly squat about pc's except how to click a mouse SHOP for instance has only 1 addon map and during the Europe daytime, voted admins are quite common, to have the 1 map that uses the only addon that the server supports, with its "Addon marker" incorporated into the name or map type, simply obscures the fact its an addon map and gives it a reasonable chance of being accidentally loaded and then kick half the players off Whereas some servers that play many addon maps would have quite a large Addon supergroup and possibly only a small Non addon supergroup. I thought about having the @ tag after the map type ie ctf@ c&h@ ctf @ c&h @ ctf_@ c&h_@ <span style='color:red'>Linux OFP servers do not have problems with spaces</span> this would work, but it would create 2 groups for every map type so if we say have 8 map types we then create 16 groups however if we precede with the @ we only have 9 groups What I am trying to create is a VERY SIMPLE convention The more basic the better 9 groups instead of 16 etc I want something that when the map selection screen opens, its as easy on the eye as i can get it Spaces make it easy on the eye, underscores dont You only have to look at the jpg to see that (Imagine removing the (bis) part of the upper listings and then compare them to the lower listings The Filename with spaces is much easier on the eye and u still get to see a good portion of the map name, certainly enough to distinguish it <span style='color:red'>So the question really is, globally do addon maps need to be distinguished from non addon maps in a clearly defined way?? or isnt it that important (Globally) and therefore intermingle addon maps with others by placing there @ in a more obscure location</span>
  20. terox

    Map filename convention

    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
  21. terox

    Map filename convention

    Zeus, our Linux test server doesnt seem to have problems with spaces in the map filename either. I believe spaces lead to clarity whereas Underscores lead to clutter I have added "rc" = Race to Map Types, or would "rac" be better Another comment on a different forum was made about the inclusions of League maps I agree with the comments made that League maps need to be distinguished in some way. But how to do it Example A (For Euro Flaspoint league Map) ctf (24) efl everonIII (1.9 v1) or Example B efl ctf (24) everonIII (1.9 v1) It would look better and be easier to find if the complete filename was preceded with the league tag. However If you say have 8 different leagues, then this would create and extra 8 map groupings 1 for each league Maps by map type and the addons group So for simplicity i believe the better way is to have the league tag after the player limit, within the map name itself (So for now I have amended the initial post with that in mind)
  22. terox

    Map filename convention

    Why do you want to use underscores instead of spaces, to split the groups up.??
  23. terox

    Addons-only dedicated public server...

    I didnt mean to start a discussion on filename conventions in a thread about servers and addons, so I have created a thread all about it which hopefully we will discuss there Map Filename Convention My last thoughts on addons and dedicated servers. The best solution to all this, is for an ingame system that 1) Checks to see if the player has the addon that the map requires 2) And if the player doesn't, then automatically download and install it for him or Have some way of including the addon in the mapfile itself
  24. terox

    Ofp servercommand kick high ping

    Don't be too hasty to kick folks who have a high ping on joining, after a few seconds, minute etc, when they are fully connected to the server, a lot of these high pingers, pings drops to a very acceptable level. Ping does not necessarily = lag
  25. terox

    Addons-only dedicated public server...

    If OFP was in its infancy, then running an addon server would probably work, however, now its lost its initial surge of newcomers, a balance has been achieved. Where old regulars that fade away are being replaced at the same rate by newbies. Adding addons to the equation may upset this balance. However maybe as some of the OFP dedicated servers, change to new games, the servers that remain will stay busy (We will have to wait and see) Having played and adminned on SHOP since OFP was first released, i really would welcome playing with new gimmicks. But not at the cost of reduced numbers of players. I love playing games of 15 v 15. or on Shrikes server 24 v 24 (Super battles) As far as the Naming of maps is concerned, we have recently introduced a file name template. And, if that map requires an addon , we simply preceed the name with @ @ = Addon required Full template system can be found on this link. PBO Filename template It states in order (Addon Required) (Map Type) (No. of Players) (Map Name) (Game Version) (Map version) Example @ C&H (32) Armourgeddon (1.85 v1).noe.pbo Every map on the server uses this template now, and when you have a hundred maps to scroll through, it really helps the admin to locate it
×