Difference between revisions of "Folderstructure"

From MechWarrior: Living Legends Wiki
Jump to: navigation, search
(root game)
(Mods-MW:LL)
Line 50: Line 50:
 
  <mod root>
 
  <mod root>
 
To make it more or less confusing.<br>
 
To make it more or less confusing.<br>
WIP: TODO rest of the folders
+
 
 +
=== Bin folders ===
 +
 
 +
=== Libs and Scripts ===
 +
 
 +
=== Game folder ===
 +
Also referred to as
 +
<MWLL game>
 +
is the folder where our actual MWLL release files belong and go.
 +
To prevent any unfair modification or cheating, a file integrity check is in place that ensures any tampering is less likely to happen.
 +
 
 +
==== Levels ====
 +
Since we don't have any ''single player'' mode, the only other mode, the one we are interested in, is the '''Multiplayer''', we all love and use.
 +
 
 +
There in:
 +
# SA
 +
# TC
 +
# TSA
 +
reside our ''maps'' in their respective folders

Revision as of 10:06, 17 June 2018

Folder Structure

Our mod has somewhat complex and quite non intuitive folder structure.
Folders.png

root

The top most, the Crysis Wars one we call the root folder, and show it like this:

<root>

or

<game root>

no matter where it resides, the rest of the game is relative to it. Many files are referenced relative to this folder.

root game

Inside of the <root> folder there are few folders of interest, one being the game folder right in it.
Our lucks has it, we have another totally different game folder elsewhere - but that one isn't not called root game folder

we show it like this

<root>/Game

This folder holds the Crysis Warhead *.PAK files - the archives of the base game.

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. The noteworthy command line parameters might be:

  1. -root (where the exec sources the settings for the user)
  2. -mod [MWLL] (where the exec picks a mod to load in advance / or not)
  3. -dx9 (a toggle, which, when present, forces use of Dx9 even if dx10 is available)

stray files

when a entity is extracted or modified in the Editor it is here where it spews files. Some end up in Libs and some in Scripts. Other files might end up in Objects, Materials or elsewhere.
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.
We call them the stray files

Levels

This is the original place where the editor was created to put files to. When making the initial terrain - the editor can be run without -mod MWLL and the initial terrain can be created while the map is here. On the other hand, this can just the same, be done in the maps final destination the mods/MWLL/Game/Levles/ folders

ScreenShots

Those are actually the minimap bitmaps and XML manifests - needed in the final stages of map creation.

Mods-MW:LL

This is where our mod is placed, we call it also like this:

<mod>

or

<mod root>

To make it more or less confusing.

Bin folders

Libs and Scripts

Game folder

Also referred to as

<MWLL game>

is the folder where our actual MWLL release files belong and go. To prevent any unfair modification or cheating, a file integrity check is in place that ensures any tampering is less likely to happen.

Levels

Since we don't have any single player mode, the only other mode, the one we are interested in, is the Multiplayer, we all love and use.

There in:

  1. SA
  2. TC
  3. TSA

reside our maps in their respective folders