Table of Contents
I. Introduction and Revision History
II. About the Author
III. Tutorials
- Cargo Sizes by Owning_Joo
- Creating New Hardpoints by CW
- How to edit the .thn script files by BobTheDog
- How to create new weapon effects by BobTheDog
- Hardpoints V.2 by Jackel
- Transparent Cockpit by Jackel
- How to change factions so you can be good to all but 1 by Reynen
- Making Energy Missiles by Rolo2020
- System Building from scratch by giskard
- Texturing by harrier
- How To Make A Black Hole By Dracon
- How To Change The Starting Ship In Multiplayer by Captain Tylor
IV. The Testing Process
V. Tools and Programs
VI. Frequently Asked Questions
VII. Random Tips, Hints and Information
VIII. Reader Emails
IX. Contact Information
X. Revisions
XI. Document Information
To find something quickly:
1.Highlight the whole section name including roman numerals.
2.Press Control and C or right click and select copy.
3.Press Control and F.
4.Press Control and V.
5.Press Enter.
===============================================================================
I. About the Author
Hi my name on the forums is bartsimpsondude2000. I had the idea for this
FAQ when I saw my favorite game had only 1 FAQ! I started to think about a
subject to work on and then it came to me. I asked everyone on Lancer's Reactor
if I could borrow some editing tutorials and they "stuck" my post on the board.
From then on I started creating this FAQ.
Ok My email is: projecteclipsor (at) msn.com (anti-spam reasons)
Please, no spam, flames, but criticism is accepted as long as it is
constructive.
===============================================================================
II. Tutorials
Here we are at the tutorials. I might need to tell you that Freelancer is one
of the most editable modern games in existence. I mean they just spilled its
guts into .ini files. They are compressed however, so you will need BiniQDU
(check the Tools and Programs section).
DO NOT USE THESE FOR AN ONLINE GAME!!! (Seriously, some might crash your
game, and others WILL get you kicked or banned! They do have a new FL version
of Punkbuster (not punkbuster but software with same purpose) that WILL detect
your edited inis!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cargo Sizes by owning_joo
First you open up your shiparch.ini. It should be in freelancer folder like
C:\program files\microsoft games\data\ships\shiparch.ini
I recommend using something like BiniQDU because you can search for words in
the .ini file.
To edit the cargo size of what ship you have to find out who makes it and what
class ship it is and the name.
Here is the ship thing for the Sabre. You go down through the list and find the
hold size part I put it in "s but dont put that in folder.
When you find the hold size just change it to what you want. I dont know if
there is any limit but highest cargo space I've edited to is 1 million.
[Ship
ids_name = 237012
ids_info = 66515
ids_info1 = 66516
ids_info2 = 66608
ids_info3 = 66517
ship_class = 3
nickname = bw_elite2
LODranges = 0, 75, 125, 1000
msg_id_prefix = gcs_refer_shiparch_borhf
mission_property = can_use_berths
type = FIGHTER
DA_archetype = ships\border_world\bw_vheavy_fighter\bw_vheavy_fighter.cmp
material_library = ships\border_world\bw_ships.mat
material_library = fx\envmapbasic.mat
envmap_material = envmapbasic
cockpit = cockpits\corsair\bw_elite2.ini
pilot_mesh = generic_pilot
nanobot_limit = 63
shield_battery_limit = 63
mass = 75.000000
"hold_size = 70"
linear_drag = 1.000000
fuse = intermed_damage_smallship01, 0.000000, 2700
fuse = intermed_damage_smallship02, 0.000000, 1350
fuse = intermed_damage_smallship03, 0.000000, 900
max_bank_angle = 30
camera_offset = 9, 33
camera_angular_acceleration = 0.060000
camera_horizontal_turn_angle = 20
camera_vertical_turn_up_angle = 10
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Creating New Hardpoints by CW
!!!Warning!!! If you arent a rocket scientist skip this section! j/k but its
confusing.
This tutorial focuses on the rotatable weapon hardpoints but fixed ones like
engines and thrusters aren't that much different, except that they are missing
a few nodes.
Recommended Utilities:
HCl's UTF Editor
Tyson Schoepflin's BiniQDU v1.1
Preparation
--------------
The feedback I got is that a lot of people don't understand the coordinate
frames, especially in the Orientation section. I must emphasise that it is VERY
IMPORTANT for you to draw diagrams as you read along, otherwise you will have a
hard time trying to understand what I'm talking about!
To make a new weapon hardpoint, first find your ship's CMP file in
..\DATA\SHIPS\(your ship's fraction)\(your ship)\ . For example my Dromedary
freighter uses a file called bw_freighter.cmp under C:\Program
Files\Freelancer\DATA\SHIPS\BORDER_WORLD\BW_FREIGHTER\. Open the file with UTF
Editor and selected "float array" under "interpret data as...".
Using the same example again, if you explore the tree structure of the file
you will notice that the first level 'tree trunks' are mainly consisted of body
parts such as "bw_freighter_lod1030109103849.3db" (fuselage),
"bw_port_eng_lod1030109103849.3db" (left wing) and
"bw_star_wing_lod1030109103849.3db" (right wing). Under these trunks there are
branches called "Hardpoints" and further under them are sub-branches labeled
"Fixed" , where all the non-moving hardpoints are stored (ie thruster, mine
launcher, shield, running lights etc.), and "Revolute" , where all the gun,
missile, torpedo/cruise disrupter and turret hardpoints are stored. You can add
hardpoints to any body parts, but I've heard that it is a really bad idea to
add hardpoints to the bay doors due to a game stability issue.
Find the right fuselage part tree trunk that you intend to mount your new
hardpoint on, select the "Revolute" sub-branch under it and click "Add node".
Rename the new node "HpWeaponXX" for gun/missile mounts; "HpTorpedoXX" for
torpedo/cruise disrupter; or "HpTurretXX" for turrets, where XX is the next
vacant mount number (if your ship has 4 guns originally, then the next gun slot
would be "HpWeapon05". Same goes for torpedo and turret hardpoints). Create 5
more nodes under this new node, and rename them "Axis" , "Max" , "Min" ,
"Orientation" , and "Position" .
Axis
-----
Select "Axis" and click Edit. I've done some experiments to find out what this
node does, but I was not able to alter the behaviour of a weapon with it and
strangely a hardpoint would work just fine with this node incomplete or even
missing. For all practical purposes this node does nothing but for the sake of
completeness just add it in and assign it the following values, which are
standard for all rotatable hardpoints:
0.000000
1.000000
0.000000
Max & Min
------------
These two nodes defines how much the weapon can rotate sideway ("sideway"
refers to the weapon, not the fuselage). If you look at an existing hardpoint,
you will notice that these two nodes have 2 elements each. The number at the
top defines the rotation limit in radians, while the number at the bottom seems
to be 0.000000 all the time. "Max" is used to define the limit to the left and
has a positive value; while "Min" is used to define the limit to the right and
takes a negative number. To make a weapon that doesn't have a rotation limit,
enter 6.283185 (=2*pi) in "Max" , and -6.283185 in "Min" , remember to put in
0.000000 for the second row.
A quick summary:
Max node = Left, Positive
Min node = Right, Negative
EXAMPLE 1: A gun with rotation limit of 30 degrees (0.523599 radians) to the
LEFT, and 40 degrees (0.698132 radians) to the RIGHT.
The Max node would be:
0.523599
0.000000
And the Min node would be:
-0.698132
0.000000
EXAMPLE 2: A turret that can rotate freely.
The Max node would be:
6.283185
0.000000
And the Min node would be:
-6.283185
0.000000
There is a way to alter the weapons' firing cones without making them
rotatable, or allow them to shoot over a wider arch than they can point their
muzzles to. This may be useful for those of you who are planning to build your
new ship around some fixed mammoth killer cannon. You can alter the following
setting in Constants.ini , which is located directly under Freelancer's Data
directory:
MUZZLE_CONE_ANGLE = 10
Note that the number is in degrees, also this setting will affect every weapon
on everybody's ships in the game. The guns in Freelancer won't shoot unless
your cursor is within their firing cone, so if you set the number too small
your weapons may sometimes seemingly refuse to fire when you maneuver too much,
especially for your fixed killer cannon.
Position
----------
Each part of the fuselage has its own coordinate frame with the same
orientation. The orientation is as follow (DRAW A DIAGRAM NOW):
Positive X: to the right
Positive Y: up
Positive Z: to the rear
Depending on which fuselage part you assign a weapon to, the Position entry is
referenced to that fuselage part's own coordinate frame. Look at the existing
hardpoints and guess some values for now, we will come back to it at the end.
Orientation - The Direct Approach
-----------------------------------------
This is the hard part that needs some vector mathematics. Each mountable
weapon has its own coordinate frame and if they are to align with the Fuselage
Coordinate Frame, ie, having their X,Y,Z axes facing the same directions, then
the gun barrel has to be pointing FORWARD with the mounting point facing DOWN.
DRAW A SEPERATED DIAGRAM OF THE WEAPON AND ITS COORDINATE FRAME NOW.
And here is the complication, the 9 elements in "Orientation" map the
Fuselage's Coordinate Frame to the Weapon's Coordinate Frame (ie, describe
where each of the Fuselage Coordinate Frame's axes are pointing on the Weapon's
Coordinate Frame). The first 3 numbers form the 3D vector for the Fuselage
Coordinate Frame's X axis, the second 3 for Y, and the last 3 for Z.
EXAMPLE 1: A gun mounted on the TOP of the fuselage facing FORWARD.
* The fuselage's X axis is pointing to the same direction as the gun's X axis,
so the first 3 elements are 1,0,0.
* The fuselage's Y axis is pointing to the same direction as the gun's Y axis,
so the next 3 elements are 0,1,0.
* The fuselage's Z axis is pointing to the same direction as the gun's Z axis,
so the last 3 elements are 0,0,1.
Sum it all up, the entry for the gun's orientation would be:
1.000000
0.000000
0.000000
0.000000
1.000000
0.000000
0.000000
0.000000
1.000000
* This is the "aligned" orientation - the three axes of the Fuselage's
Coordinate Frame are aligned with the Weapon's Coordinate Frame's three
corresponding axes.
EXAMPLE 2: A gun mounted on the RIGHT side of the fuselage facing FORWARD.
* The fuselage's X axis is pointing to the same direction as the gun's Y axis,
so the first 3 elements are 0,1,0.
* The fuselage's Y axis is pointing to the exact opposite direction as the
gun's X axis, so the next 3 elements are -1,0,0.
* The fuselage's Z axis is pointing to the same direction as the gun's Z axis,
so the last 3 elements are 0,0,1
Sum it all up, the entry for the gun's Orientation would be:
0.000000
1.000000
0.000000
-1.000000
0.000000
0.000000
0.000000
0.000000
1.000000
EXAMPLE 3: A turret mounted UNDER the fuselage facing to the REAR.
* The fuselage's X axis is pointing to the same direction as the turret's X
axis, so the first 3 elements are 1,0,0.
* The fuselage's Y axis is pointing to the exact opposite direction as the
turret's Y axis, so the next 3 elements are 0,-1,0.
* The fuselage's Z axis is pointing to the exact opposite direction as the
turret's Z axis, so the last 3 elements are 0,0,-1
Sum it all up, the entry for the turret's Orientation would be:
1.000000
0.000000
0.000000
0.000000
-1.000000
0.000000
0.000000
0.000000
-1.000000
EXAMPLE 4: A gun mounted on a 45 degrees slope (the slope faces the morning
sun) on the RIGHT side of the fuselage facing FORWARD. I will stick to the unit
vector principle (keeping the hypotenuse = 1) for less confusion.
* The fuselage's X axis can be described as y=x on the gun's coordinate frame,
so the first 3 elements are 0.707107,0.707107,0. (Remembering 0.707107^2 +
0.707107^2=1^2 from trigonometry; alternatively you can forget about the unit
vector principle and use 1,1,0 instead, but it might get confusing if you have
any angles other than 45 degrees.)
* The fuselage's Y axis can be described as y=-x on the gun's coordinate
frame, so the next 3 elements are -0.707107,0.707107,0.
* The fuselage's Z axis is pointing to the same direction as the gun's Z axis,
so the last 3 elements are 0,0,1.
Sum it all up, the entry for the gun's Orientation would be:
0.707107
0.707107
0.000000
-0.707107
0.707107
0.000000
0.000000
0.000000
1.000000
If you screw up the orientation matrix, the weapon you mount on the new
hardpoint will appear somewhat transparent in the ship dealer, and will
malfunction in flight.
And if you really want it here you go:
Orientation - The Smart Aerospace Engineer's Approach
--------------------------------------------------------------------
If you are trying to mount your hardpoints on some odd-facing surfaces, it
will kill a lot of your brain cells trying to come up with the orientation
matrix directly. In this case we need to use a little bit more maths to save
us the trouble. Make sure you know how to do matrix multiplication, else look
up here for a quick (5 minutes) but sufficient primer.
What we are going to do here is taking a different approach by breaking the
problem down into 3 easier to manage questions:
1) Starting from the "Aligned Orientation", how much in radians do I want to
rotate the weapon around its X-axis?
2) How much in radians do I want to rotate the weapon around its Y-axis?
3) How much in radians do I want to rotate the weapon around its Z-axis?
("Aligned orientation": Recalling that if the Weapon's Coordinate Frame is to
be aligned with the Fuselage's Coordinate Frame, then the gun barrel has to be
pointing FORWARD with the mounting point facing DOWN.)
We are going to use this ugly looking formula 3 times, each for the X,Y and Z
axes respectively:
Where,
* {u1;v1;w1} is the Fuselage's Coordinate Frame axis you are trying to
transform. The Freelancer game engine wants the transformation of all three
axes (hence 9 elements), so in this case use the formula 3 times, once for
{1;0;0} (ie. the X-axis), once for {0;1;0} (ie. the Y-axis), and once for
{0;0;1} (ie. the Z-axis).
* {u;v;w} is the resulting transformed axis that forms the elements in the
orientation matrix.
* Phi (that circle with a stroke through it) stands for the rotation you want
around the X-axis (ie. pitch).
* Theta stands for the rotation you want around the Y-axis (ie. yaw).
* Psi (that trident-like symbol) is the rotation you want around the Z-axis
(ie. roll).
Whether the rotation is positive or negative is defined by the "Right Hand
Rule". Hold up your right fist and stick up your thumb, if your thumb points
towards the positive direction of the axis, then your other fingers signifies
the positive direction of rotation around it.
To get your orientation matrix, follow these steps:
1) Figure out what Phi, Theta, Psi values you want, plug them into the formula.
2) Replace {u1; v1; w1} with {1, 0, 0}.
3) Solve the equation to get {u; v ;w}, that's the first 3 elements in the
orientation matrix.
4) Replace {u1; v1; w1} with {0, 1, 0}.
5) Solve again, that's the middle 3 elements in the orientation matrix.
4) Replace {u1; v1; w1} with {0, 0, 1}.
5) Solve once more, that's the last 3 elements in the orientation matrix.
6) Put your orientation matrix into UTF editor and try it out in the game, if
you don't like the result, go back to step 1.
It is definitely much less tedious if you get some computational maths package
to do the calculations for you.
Activating The Hardpoint
-------------------------------
That's it for orientation and the new hardpoint is now fully defined. The next
step is to enable it in shiparch.ini which is located in ..\DATA\SHIPS\ . But
before you do that, look up here for the unique ID number of your ship. Once
you have the ID number, open shiparch.ini with BiniQDU and find your ship. If
you created a gun hardpoint, find the lines starting with "hp_type =
hp_gun_special_X, HpWeapon01, HpWeapon02, ..." and add your new hardpoint to
the end of each line. Notice that X stands for the class of guns, so if you
want your new hardpoint to take every gun in the game, add it to the back of
all 10 lines. Unless you are modding the Eagle, Titan or Sabre, which take
class 10 guns and missiles by default, you will need to add the missing lines
for the higher classes. Just follow the pattern. Same goes for torpedos/cruise
disrupters and turrets, under the lines "hp_type = hp_torpedo_special_X, ..."
(there are 2 classes of torpedos/cruise disrupters) and "hp_type =
hp_turret_special_X, ..." (10 classes) respectively.
Remember to save your work. The last step would be to run the game, put a
weapon on your new hardpoint and see where it goes, then come back to refine
the hardpoint's position.
That's it for adding hardpoints! Enjoy your overloaded super gunship!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
How to edit the .thn script files by BobTheDog
Part 1
Ok, so ya want to edit a script, right? well, today we're gonna focus on the
main menu background, the one with the station in front of a planet with the
ships and transports flying across.
First off, you need the .thn uncompiler, BiniQDU, and the UTF Editor
Both of which can be found in the Tools and Programs Section
Now, once you have those, go into DATA\SCRIPTS\INTRO and copy gasminer3.thn to
wherever you unzipped the .thn decompiler to. decompile it and open it up with
notepad.
Now, you are probably going "What's this? this isn't Freelancer coding!" and
you'd be right. It's scripted in LUA code. But it's fairly straightforward,
especially if ya know C++ or something like it.
I'm not entirely sure what time unit is used in these, so just leave them
alone for now.
Part 2
Ok, now every FL script (to my knowledge) begins with a duration declaration,
and then a scene entity, and ya can just copy those if ya make a new script.
here's how things work in FL scripts:
Everything has to be declared. You can only use things from solararch.ini,
shiparch.ini, effects.ini, and the starspheres and nebulaspheres.
so, here's how to declare a ship:
{
entity_name="Ships_li_dreadnought", <-- this is the name used to reference it
in this script
type=COMPOUND, <-- must be this for ships
template_name="li_dreadnought", <-- what to use from shiparch.ini
lt_grp=4,
srt_grp=0,
usr_flg=0,
flags=LIT_DYNAMIC,
spatialprops={
pos={ <-- position to start at... only used is stationary
7760.895996,
612.4628300000001,
-4181.624023
},
orient={ <-- rotational vectors
{
-0.955097,
0,
-0.296293
},
{
0,
1,
0
},
{
0.296293,
0,
-0.955097
}
}
},
userprops={ <-- I assume this tells it where to get the template from...
category="Spaceship"
}
},
now, you can mae the template anything from shiparch.ini
we have a ship, now let's make it follow a path:
This is a path from gasminer3.thn:
{
entity_name="Path_1_copy_1",
type=MOTION_PATH,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0,
spatialprops={
pos={
5,
6.576355,
55
},
orient={
{
1,
0,
0
},
{
0,
1,
0
},
{
0,
0,
1
}
}
},
pathprops={
path_type="CV_CROrientationSplinePath",
path_data="OPEN, {7760.895996,612.463013,-4181.623535},
{1.000000,0.000000,0.000000,0.000000}, {7465.413574,612.463013,-3846.421143},
{1.000000,0.000000,0.000000,0.000000}, {7569.932129,612.463013,-3511.218262},
{1.000000,0.000000,0.000000,0.000000}, {7474.450684,612.463013,-3176.015137},
{1.000000,0.000000,0.000000,0.000000}, {7358.968750,612.463013,-2840.812256},
{1.000000,0.000000,0.000000,0.000000}, {7283.486816,612.463013,-2505.608887},
{1.000000,0.000000,0.000000,0.000000}, {7188.005371,612.463013,-2170.406006},
{1.000000,0.000000,0.000000,0.000000}, {7092.523438,612.463013,-1835.202759},
{1.000000,0.000000,0.000000,0.000000}, {6997.041504,612.463013,-1500.000000},
{1.000000,0.000000,0.000000,0.000000}, "
}
},
all the numbers at the bottom are points for the path to follow, i'm not sure
how to calculate them, tho. What you CAN do is edi the pos={ section:
pos={
5, <-- positive is right, negative is left
6.576355, <-- positive is up, negative is down
55 <-- positive is forward, negative is back
},
I'm assuming that these paths are calculated from the center of the scene.
Now, you need to have the ship go down the path... under the events={ section,
at the end of the declarations, you would put:
{
0, <--this tells it how many time units to delay the action (I think)
START_PATH_ANIMATION,
{
"Ships_li_dreadnought", <-- which entity to put on the path
"Path_1" <-- which path to use
},
{
duration=60, <I entity_name="FX_ge_lbd_engine_01" template_name="gf_li_largeengine03" target_part="hpengine01" entity_name="smoke1" template_name="gf_prisonattack_bigsmoke" entity_name="smoke2" template_name="gf_prisonattack_bigsmoke" entity_name="smoke3" template_name="gf_prisonattack_bigsmoke" entity_name="smoke4" template_name="gf_prisonattack_bigsmoke" entity_name="smoke5" template_name="gf_prisonattack_bigsmoke" entity_name="smoke6" template_name="gf_prisonattack_bigsmoke" entity_name="smoke7" template_name="gf_prisonattack_bigsmoke" entity_name="smoke8" template_name="gf_prisonattack_bigsmoke" entity_name="smoke9" template_name="gf_prisonattack_bigsmoke" target_part="hpturret_s2_01" target_part="hpturret_s1_01" target_part="hpturret_s1_02" target_part="hpturret_s1_03" target_part="hpturret_s1_04" target_part="hpturret_s1_05" target_part="hpturret_s1_06" target_part="hpturret_s1_07" target_part="hpturret_s1_08">> this produces a funky-looking
CIRCULAR BAND of miniature accretion discs... there has to be another
parameter (disc/plane?) to tie bh.ini into the big picture (and to add jets,
which are currently MIA).
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
How To Change The Starting Ship In Multiplayer by Captain Tylor
I've not yet seen a tutorial for flying something other than that sissy
starflier in every MP server I go to, so here's a tutorial for your reference,
to change the ship new characters get without them needing to download
anything. This type of mod can work with the patch, so long as your ship
doesn't have anything "illegal" like a uber shield or hull, or some other
infinite item. Best of all, you don't need to modify two or three files like
maybe other tutorials have stated. The only file you'll be modding is
mpnewcharacter.fl
You'll need to use a ini decompressor/extractor, like BiniQBU or BWS ini
editor. I prefer using a command line decompressor with a batch file, but you
should use what seems most comfortable to you. You'll also need a reference to
decipher those IDs. I recommend using *** IDS_NAMES *** to Friendly Names
(
http://www.lancersreactor.com/t/forum/t ... _id=18&Top
ic_Title=%2A%2A%2A+IDS%5FNAMES+%2A%2A%2A+to+Friendly+Names&forum_title=Freelanc
er+Editing+Forum&cat_title=&M=False) created by vovin. It deciphers the IDs in
the following files:
DATA\SHIPS\loadouts.ini
DATA\SHIPS\ships_arch.ini
DATA\EQUIPMENT\weapon_equip.ini
DATA\EQUIPMENT\engine_equip.ini
DATA\EQUIPMENT\misc_equip.ini <--powerplants
DATA\EQUIPMENT\st_equip.ini <--shields
DATA\EQUIPMENT\select_equip <--commodities
I want to make this clear, you won't be altering these files. extract them to
a txt format and have them available as you make your mod.
PART 1:
First, let's take a look at the default ship used. This is pulled directly
from the loadout.ini file in the DATA\SHIPS folder:
[Loadout
nickname = msn_playerloadout
archetype = ge_fighter <--ship referenced by nickname in shiparch.ini
equip = ge_gf1_engine_01 <--engine
equip = shield01_mark01_lf, HpShield01 <--shield
equip = ge_fighter_power01 --powerplant
equip = ge_s_scanner_01 <--scanner. comes in two flavors
equip = ge_s_tractor_01 <--tractor beam. usually the same for every ship.
equip = ge_s_thruster_01, HpThruster01 <--thruster
equip = li_gun01_mark01, HpWeapon01 <--justice Ilaser
equip = li_gun01_mark01, HpWeapon02 <--justice I laser
equip = LargeWhiteSpecial, HpHeadlight <these>
cargo = ge_s_battery_01, 3 <--batteries on board
cargo = ge_s_repair_01, 3 <--nanos on board.
from archtype on down, you can copy and paste the above into your
mpnewcharacter.fl file, but it still won't work properly. first you need to
change
archetype = ge_fighter
to this:
ship_archetype = ge_fighter
then you need to comment out
%%PACKAGE%%
at the bottom. just put a ; in front of it so it'll look like
;%%PACKAGE%%
instead. You can start up a MP server but won't see any noticable change
however, since it's the same ship.
Now we will try to change the default ship to the pirahna, complete with
appropriate weapons. After decompressing the above ini files into txt ones, I
pasted in the deciphered ID names for easy reference. The pirahna ship will be
have this nickname, pulled right from shiparch.ini:
nickname = bh_fighter
now I go to the loadouts.ini file and run a search for bh_fighter, and get
this:
archetype = bh_fighter
equip = ge_pf_engine_01
equip = npc_shield02_mark02, HpShield01 <NPC> my_gun100 - its easy to
keep track of then, and easy to modify too.
Once done (make sure you entries nicknames are correct and also the ids
number in the goods.ini file) then make sure nicknames are correct for selling
guns in the market_misc.ini file (sells guns etc).....copy an older entry from
a base for a gun, then just change the nickname to match the package nickname
for the gun in the weapons_good.ini
Commodities
Several files also need adjusting here:
Select_equip.ini
Goods.ini
and then also the market_commodities.ini as well - only change the
commodities_per_faction.ini if you want NPC's to carry your commodity (i think
- i haven't actually tried this - just making an 'educated' guess! Let me know
if wrong.
Once again - check ids numbers here, nicknames especially too! The goods.ini
file and so on are sensitive to ids numbers and nicknames - so they are the
prime culprits. The icons don't affect whether you crash or not at all - so it
aint that stuff!!
A2:Check: Did you try to change other values in the market_commodities.ini,
market_ships.ini and market_misc.ini? If so - what did you change? Always
remember what you changed, and be prepared to change it straight back if there
are crashes. There ARE limits to what you can do!
Q:There are no people on my bases, in the rooms, anywhere at all!!
A1:Check: The mbases.ini file. Have you made an entry for your base here? Did
you give it a population, but remember the nicknames and so on for you base
correctly-- and change the chaps accordingly?! Check away
Q:I made it so that the base was populated, but now whenever I want a mission
it tells me to get on better with the base faction first!
A1:Check: Oh nasty problem in the fact that goodbye to several hours of life
here! You need to do the following:
[iMbases.ini file - open this up, and take a peek. Inside you will see the
following:
example
[BaseFaction
faction = li_n_grp
weight = 13
offers_missions = true
mission_type = DestroyMission, 0.000000, 0.112387, 30
This will actually be this do to corruption when you open the file up!
offers_missions = mission_type = DestroyMission, 0.000000, 0.112387, 30
See the problem is that offers_missions = true has had the true part taken
out by the application used to decrypt the ini files (biniq). Time for a 2
hour manual edit of the file back to normal!
Q:No missions are ever on offer at my base!!
A1:Check: That you have included some vignettes into your systems ini file
example - Li07.ini file. A typical vignette entry looks like this:
Example: another of mine
[zone
nickname = zone_Li07_destroy_vignette_6
pos = 43343, 0, -1791
shape = SPHERE
size = 10000
sort = 99.500000
vignette_type = field
Make sure that you have nicknames that are unique too!!
A2:Check: that in your mbases.ini file you actually have offers_missions =
true at all! Also - that your population offers missions as well.
Q:I don't get rumours/bribes from my stations population or bartender!
A1:Check: Back to Mbases.ini file - as this is where your problem lies - has
your bartender got any bribes or rumours to tell you set for him?
EXAMPLE: Here is one taken from the Manhat bartender - similar for you
bribe = li_p_grp, 10000, 16101
bribe = co_be_grp, 10000, 16100
bribe = co_nws_grp, 10000, 16100
bribe = co_kt_grp, 10000, 16100
bribe = gd_bh_grp, 10000, 16100
rumor = base_0_rank, mission_end, 2, 131232
rumor = base_0_rank, mission_end, 3, 131233
rumor = base_0_rank, mission_end, 1, 131222
rumor = base_0_rank, mission_end, 1, 131225
rumor = base_0_rank, mission_end, 1, 131226
rumor = base_0_rank, mission_end, 1, 131228
Do you have parts looking like this below him?
You can create custom rumours and stuff as well - also custom bribes for the
base too - just need for rumours to set your own rumour in the ini file- then
slap its ids number in there, and for bribes - add your faction of choice, and
set the values!
Q:I crash whenever I open the navmap!
A1: Have you overloaded the system/navmap?
I experienced this one in NY, after checking and rechecking the loadouts file
which I had changed,along with all the other little files i had changed, i
turned back to one i hadn't touched for an age..........the system file - why
would it crash when openening? I did trial and error - i thought i must have
overloaded my system file (its NY by the way!) so i removed the load of
objects i had, then i removed the jumphole i made to another system for quick
testing. I also attempted to change the visablitity o the internal NY
jumpholes - but too no avail = however, removing the jumphole and nav bouys
did the trick. This harked back to what Giskard was telling me about manhatten
having perhaps the maximum amount of objects allowable in a system - if you
add one more it removes other ones or something. I also thought of something
else that was mentioned -i believe this came from Reynen - that you cannot
have more than 8 jumpholes/gates to ta system - well, i had ten i think (2
internal J/H's. one to Texas and one to colorado, 1 to mytest system - then
the jumpgates - alaska., texas, colorado, LA, Magellan) - 10 in all, however,
they all worked to use though - so unless they cause crashes due to the nav
map?? Hmm - however, if you get a stumper and you have lots of objects, or
loads of jumpholes - give this a try! My system is now working again - and
luckily i have nothing to remod as i save files first (incase they aren't the
cause - at which point, i can just put the old one back in rather than remod
the damned thing!!)
===============================================================================
VII. Random Tips, Hints and Information
A few little hints on modding
1) Always back up your files regularly!
2) Build the mod in FLMM, then whenever you make several succesful
adjustment, create a zip of your folder to keep a 'backup' before progressing!
3) Always, no matter how tedious, check individual changes until you are very
comfortable with modding. If you mod three things, then find you crash - it is
much more difficult to narrow it down, than making one!
4) I always copy old entries, then change them, instead of writing new ones.
One thing it will do is erase 90% of spelling errors!! Also it makes it
quicker. For systems, you won't even need to give objects new ids names to
check that stuff works at all, so its quick, simple and easy! Once you find
your asteroids working, or your jumpholes/gates working, give them the custom
ids names at that point!
5) Don't hit your computer - it is your mistake......also, it could then be
an expensive mistake!
Basic rule of thumb for system crashes ...If you can get to your system - but
you crash in various parts as you go round, then your problems lie in the
encounters you have set up (see Frequently Asked Questions)
===============================================================================
VIII. Reader Emails
1. Neal Eckett
-------------------------------------------------------------------------------
Hi,
Thought you may be interested, you may already know this but I have found the
ini file to control the thrusters speed.
It is in \Data\Equipment and is called st_equip.ini
I have the advanced thrusters on my ship and in the top of this file found
the mathing [Thruster] section. It is ge_s_thruster_04 (ids_name = 263740)
The higher you set the max_force parameter, the faster you go when you hit
tab! Also, you can change the power drain. I have set my max thrust to 600000
and power drain to 10. It kicks ass. I can outrun any ship and also now can
cross the maps as if they had trade lanes in them (good for exploring the
maps!).
Hope you find this useful.
Neal
-------------------------------------------------------------------------------
===============================================================================
IX. Contact Information
MSN: bartsimpsondude_2000 (at) msn.com
email: projecteclipsor (at) msn.com (be sure to put Subject as FAQ!!!)
===============================================================================
X. Revisions
1.0 (8-4-03,14:39) Just sent the guide to GameFAQ's awaiting submission...
First write.
1.1 (8-5-03,12:52) I added some more tutorials.
1.2 (10-9-03, 18:08) Sorry for taking so long but i changed some stuff fixed
typos... etc. Still awaiting submission
1.21 (10-9-03, 21:40) Added some stuff to warn against using online (DON'T DO
IT!) and I hope they will accept my faq with the changes
1.3c (10-10-03, 16:12) Ok, My FAQ was accepted at version 1.1. I just added
some to FAQ and Random Tips
1.4c (10-24-03, 0:37) Added another FAQ, put faq list in top.\
1.41. (10-24-03, 1:13) Random spellchecks
1.5c (1-19-04, 11:04) Long time ... well I finished putting up harriers
tutorial...
1.51o (2-13-04, 17:49) New letter with a tip today and new section (Reader
Emails)
1.52m (2-13-04, 18:35) New Tutorials!
1.53x (2-14-04, 10:13) Added some nice pictures of 1s and 0s and a numbery
thing I found on the net.
1.54x (2-20-04, 18:54) Added a change of logo...
===============================================================================
XI. Document Information
I would like to thank:
God: Obviously...
Computer Gaming World: for releasing the demo to get me hooked
Microsoft: For Making the Game
The Folks at Best Buy: For supplying the game
Reynen: For his Tutorial
CW: For his Tutorial
Jackel: For his Tutorial
BobTheDog: For his Tutorial
Rolo2020: For his Tutorial
giskard: For his Tutorial
Owning_Joo: For his Tutorial
Chips: For compiling information for the FAQ and Random Tips
harrier: For his tutorial
Captain Tylor: For his tutorial
Dracon: For his tutorial
Osrevad: For that ASCII art up there (check logo for contact info)
The Folks at Lancers Reactor!!:For all their support and Random Tips and FAQ
questions
