Reminder: Internet Explorer 6 or below are NOT supported.





There are currently 45 users playing Freelancer on
42 servers. | March. 4, 2021 |
The Starport Forum Index
>
The Shipyard
>
Tutorials
>
The Magic behind Random Missions and Difficulty
Browsing this Thread:
1 Anonymous Users
The Magic behind Random Missions and Difficulty |
||||
---|---|---|---|---|
Just can't stay away
![]() ![]() Joined:
2010/2/17 20:45 From Germany
Group:
Registered Users Senior Members
Posts:
487
![]() |
Table of Contents:
Difficulty A basic requirement and variable for random missions is the Difficulty. It is an arbitrary decimal number in a range of [0, 100] (meaning 0 and 100 are included). If needed the maximum difficulty can be adjusted by those offsets: Code: content.dll, 1143D4, 100f = maximum value of misn difficulty Difficulty Calculation for Job Offers (mBase.ini) A key to understand how Difficulty works is the way how it is used and calculated. This is unfortunately not very easy to understand at first. The main use is within mBase.ini where the values are set which difficulty a player can get from a base or NPC. The difficulty number displayed in-game when reading a mission offer has a somewhat direct connection to the chosen technical difficulty behind. Apparently those in-game numbers are hard-coded somewhere for specific difficulty values. Commonly the mission_type parameter can be understood as: Code: mission_type = DestroyMission, <minDiff>, <maxDiff>, <weight> The weight is an arbitrary value, used relative to the sum of weights given. E.g. having one faction offer missions with weight=1, and another faction offering with weight=2 makes the second faction's missions appear in 2 out of 3 cases. minDiff and maxDiff are important for the calculation of the real Difficulty that will be available for the player. Especially important is to note that maxDiff is not necessarily really the maximum. The calculations are as follows: Single Player Code:
Multi Player Code: rnd is a random value in range of [0, 3) Looking especially on the first part of the multiplayer-specific calculation shows that maxDiff is not a constant value, but is getting multiplied by a random factor. This can make multiplayer missions go beyond the naively intended levels. To understand the influence of the minDiff and maxDiff values in those calculations I do recommend to look on a graph plot for some simple values. As an example in multiplayer when minDiff is 0 and maxDiff is 1 in the final calculation, the graph looks like this If minDiff and maxDiff are swapped interesting results like this can be achieved. In those plots the left axis shows the probability to get the mission, whereas the lower axis shows the difficulty level to get. To limit the difficulty in multiplayer between the minDiff and maxDiff value, the following patch can be applied on Content.dll using bwpatchw. Code: # Make MP job difficulty exactly between min and max difficulty in mbases.ini. Amount of NPCs created by Difficulty and NPC Level (npcranktodiff.ini) It is possible to define exactly how many NPCs of a specific level are being created for a specific Difficulty. This is handled within the npcranktodiff.ini. A line looks as follows: Code: NpcRank = <NPC Level>, <Difficulty for 1 Ship>, <Difficulty for 2 Ships>, <Difficulty for 3 Ships>, ... Important to note:
The game uses a table of weights to define a preference for the amount of ships being spawned. It is as follows: Code: Ships SP MP The weights here are again relative to their sum. E.g. in multiplayer the sum is 27, so 4 ships get spawned in 9 out of 27 cases (33.3%). As you can see, 1 ship has weight of 0. This means the game never will pick an NpcRank where the Difficulty for only the first ship would match. This table is very important to keep in mind. At any Difficulty picked, there always should be NpcRanks defined that cover all those ship counts. If you notice your job-board being more empty than it should be, it could be that the game tries to pick a ship count which is not provided for the current Difficulty. This table can be adjusted at the offset 11CC58 in Content.dll. First are the weights for singleplayer (starting for 0 ships, 1 ship, 2 ships, etc.) and after that for multiplayer (also starting for 0 ships, 1 ship, ...). If you want to allow NpcRanks with more than 8 ships being spawned, you must create your own weight-table. Code: content.dll 0F8A4B 58CCFB->00CBFC = use 30-float array at 12CB08 (created manually!) for SP ship weighting vector ~adoxa Requirements to have Missions offered on a Base There are 4 requirements that must be met to have a mission of a specific Difficulty being offered to a player:
This sounds quite daunting, so let's explain this on an example: We want to have some faction offer missions against fc_lr_grp in our system. For this we at first need a mission zone: Code: [Zone] Now we must make sure the enemy spawns within this zone, so it will get selected by the game to be associated with this enemy faction. Code: [Zone] Now we must find out which Difficulty our mission may have. For this we check in our mBase.ini: Code: mission_type = DestroyMission, 0, 0.112387, 100 With this value we now go into our npcranktodiff.ini file and look which line might match. Keep in mind the game has certain weights on how many ships it prefers to spawn (see above chapter). One of the possible NpcRanks might be: Code: NpcRank = 1, 0.00985, 0.03569, 0.07754, 0.13539, 0.20923, 0.29908, 0.40493, 0.52677 With this we know that we want to spawn level 1 NPCs. Now we must make sure fc_lr_grp has at least one ship matching this with an npc_class of class_fighter: Code: [NPCShipArch] We see that the level=d1, matching our NpcRank. And we see the npc_class contains d1 and class_fighter, so it also can spawn the ship. Important to know is that one ship with the required level must exist. But it does not need to be the same ship that is being spawned. The ships that will be spawned are determined by their matching npc_class label. Meaning that if your ship has d1, but npc_class d100, it will not be spawned. You can and must have at least one (but it can be another) ship with a matching npc_class diff-label for d1, and class_fighter. Important here is that whatever ship has the matching npc_class must match the level +1. So we could say we have a level d2 ship with npc_class=diff1, class_fighter, it would be able to be spawned. But only if there is another ship defined somewhere that has level=d1. This may look like this and still get spawned in our d1 mission: Code: [NPCShipArch] Payment by Difficulty (diff2money.ini) Defining payments for specific Difficulties is very easy and straight-forward to be done in diff2money.ini. A line looks as follows: Code: Diff2Money = <Start Difficulty>, <Payment> You can add as many or as few of those lines as you like. The payments between each defined Difficulty are linearly interpolated. You should at least provide a line for Difficulty 0 and 100 to allow the game to compute any payments between.
Posted on: 1/23 0:36
|
|||
How to create .SUR files - Tutorial | ||||
|
Re: The Magic behind Random Missions and Difficulty |
||||
---|---|---|---|---|
Just popping in
![]() ![]() Joined:
1/22 12:23 Group:
Registered Users
Posts:
12
![]() |
This is great, thanks for sharing! Will find this really useful.
Posted on: 1/27 3:13
|
|||
|
Re: The Magic behind Random Missions and Difficulty |
||||
---|---|---|---|---|
Home away from home
![]() ![]() Joined:
2009/8/16 2:58 From Qld, Aus.
Group:
Registered Users FLServer Admins Trusted Speciality Developers Senior Members
Posts:
1979
![]() |
Quote: The weight is an arbitrary value, usually chosen between 0 and including 100, in a way that the sum of all mission_types of a base are 100. This may not be necessary however. It's relative to the sum. Seemingly Freelancer devs chose to express it as a percentage, but any value can be used. E.g. three missions each with a weight of 1 means any is equally likely (one in three); three missions with weights of 1, 2 and 3 means the first is unlikely (one in six), the second is less likely (one in three [2/6]) and the third is likely (half [3/6]).
Posted on: 1/27 5:21
|
|||
|
Re: The Magic behind Random Missions and Difficulty |
||||
---|---|---|---|---|
Just can't stay away
![]() ![]() Joined:
2010/2/17 20:45 From Germany
Group:
Registered Users Senior Members
Posts:
487
![]() |
Thanks for the clarification, I edited the post.
Posted on: 1/27 10:46
|
|||
How to create .SUR files - Tutorial | ||||
|
Re: The Magic behind Random Missions and Difficulty |
||||
---|---|---|---|---|
Just popping in
![]() ![]() Joined:
1/22 12:23 Group:
Registered Users
Posts:
12
![]() |
Thanks for clarifying that. Also, hello from a fellow QLDer, haha. Small world (universe?).
Posted on: 1/28 1:59
|
|||
|