Folderstructure - Revision history

Fire-hound: /* Map */

2019-08-18T17:07:47Z

‎Map

2019-08-18T16:47:23Z

‎ScreenShots

2019-08-18T16:44:56Z

‎stray files

2019-08-18T16:43:15Z

‎Bin folders

2018-06-17T08:25:44Z

‎Map

2018-06-17T08:24:53Z

‎Map

2018-06-17T08:24:12Z

‎Map

2018-06-17T08:23:32Z

‎Map

2018-06-17T08:22:25Z

‎Game folder

2018-06-17T08:22:11Z

‎Game folder

@@ Line 86: / Line 86: @@
 For this to be of no concern, it is '''''strongly advised''''' for the map's ''final save'' and ''export to engine'' the '''actual location''' be used.
   Move the map folder to the actual play location and save it there.Work on it until all issues of relocation are ironed out. Then only export it and submit for further testing.
-Obeying to this guideline will save many a headache and streamline the map deployment the most.
+Obeying to this and [[Maprelease|Map Release Guidelines]] will save many a headache and streamline the map deployment the most.

@@ Line 43: / Line 43: @@
 === ScreenShots ===
 Those are actually the minimap bitmaps and XML manifests - needed in the final stages of map creation.
 == Mods-MW:LL ==

@@ Line 34: / Line 34: @@
 Those files can't really be referenced from the map files. For a Map to work, they need be shiped ''aside'' the map folder - and can't be ''automagically'' downloaded.<br>
 We call them the ''stray files''<br>
 === Levels ===

@@ Line 23: / Line 23: @@
 === Bin folders ===
-Those are the folders that hold our game and editor executables. Only interesting if one want's to make shortcuts to launch the game circumventing the launcher. Note, tho, the launcher takes care of certain stuff - you on ''manual override'' this way.
+Those are the folders that hold our game and editor executables. Only interesting if one want's to make shortcuts to launch the game circumventing the launcher. Note, tho, the launcher takes care of certain stuff - you who are on ''manual override'', come this way.
 The noteworthy command line parameters might be:
 # -root (where the exec sources the settings for the user)

@@ Line 82: / Line 82: @@
 The map *.CRY alone, can, however be created and/or edited pretty much anywhere. However, as the Sandbox2 saves it, any imported asset is being referenced relative to the <root>, as seen above.<br>
 All the while the map will work nice in the editor, but once exported to his '''level.PAK''', references will be hard coded to the maps relative position in respect to the <root> and the position the map was opened from.<br>
-For this to be of no concern, it is '''''strongly advised''''' for the map's ''final save'' and ''export to engine'' the actual location be used.
+For this to be of no concern, it is '''''strongly advised''''' for the map's ''final save'' and ''export to engine'' the '''actual location''' be used.
   Move the map folder to the actual play location and save it there.Work on it until all issues of relocation are ironed out. Then only export it and submit for further testing.
 Obeying to this guideline will save many a headache and streamline the map deployment the most.

@@ Line 77: / Line 77: @@
 # The <MWLL game> *.PAK files do overlay them all with the respective zPatch.PAK being "on top".
 # our '''map''' zip is in it's respective <MWLL game>/Levles/Multiplayer/<gamemode dir>/<map name dir> location
-# any file within the game directory is to be prepended the path to the <root> :
+# any file within the game directory is to be prepended with the path to the <root> :
   mods/MWLL/Game/Levels/Multiplayer/[TC|TSA|SA]/<mapname>/<local path> to be accessible to the game engine.

@@ Line 75: / Line 75: @@
 As the game opens the map for playing we have following file structure at sight:
 # The <root game> *.PAK files are overyaled relative to the <root>/Game folder with the zPatch.PAK overlaying them all
-# The <MWLL game> *.PAK files are overlay them all with the respective zPatch.PAK being "on top".
+# The <MWLL game> *.PAK files do overlay them all with the respective zPatch.PAK being "on top".
 # our '''map''' zip is in it's respective <MWLL game>/Levles/Multiplayer/<gamemode dir>/<map name dir> location
 # any file within the game directory is to be prepended the path to the <root> :

@@ Line 59: / Line 59: @@
   <MWLL game>
 is the folder where our actual MWLL release files belong and go.<br>
-To prevent most unfair modification or cheating, a file integrity check is in place that ensures any tampering is less likely to happen.
+To prevent most unfair modifications or cheating, a file integrity check is in place that ensures any tampering is less likely to happen.
 ==== Levels ====