Dev's Limit Breaking 101 Techniques

I found a way to have numbers under 1.0 on the drag_modifier variable on [Zones], meaning that 0.5 or similar will increase speed instead of reducing it.

!! Please do a backup of the file, this was done with Ghidra and needs testing !!

Common.dll

OFFSET 000D7A60
CHANGE: 7A -> EB

OFFSET 000D7AC0
CHANGE: 7A -> EB

OFFSET 000D7AF0
CHANGE: 0F 85 73 02 00 00 -> 90 90 90 90 90 90

Your first two offsets seem off; I see them at D7A6F & D7ACC. May as well change the first one to EB 65, thus skipping the second.

@Adoxa how exactly does “include external equipment in cargo size” limit breaker works?

some offsets were sitting in there in a folder

1.Turn off non-music sounds
SoundManager.dll+89B8 (function loads sounds once)
74 -> EB 

2.Turn off combat chatter
Content.dll+12E368
01 -> 00 

3.Turn off rendering of static debris(collisions are not affected)
Freelancer.exe+122669
74 -> EB

4.Thickness of F1 menu/Inventory Rectangle bars, make it more thick
Freelancer.exe+1A36B3(bot line)
Freelancer.exe+1A374A(right line)
Freelancer.exe+1A37B6(top line)
Freelancer.exe+1A383A(left line)

68 A6 9B 44 3B(0.002) -> 68 6F 12 0C 3C(0.008)

5.Icon size multiplier
Freelancer.exe+1D748C
Default is 0 float, can increase up to 0.03

6.Neural net icons will always flash
Freelancer.exe+15B28F
74 05 -> 90 90

7.Change color of clicked (toggled on) icons (00-FF 1 byte minimum/maximum value)
Freelancer.exe+15B22C RED 
Freelancer.exe+15B231 GREEN
Freelancer.exe+15B236 BLUE

default color is yellow

8.Turn off rendering background universe
Freelancer.exe+152E7C

74 -> EB

9.BUGFIX for FLHook RequestSpaceScript
Server sided cutscenes crashes for client due to a bug 
.thn files that you want to play must be in, /DATA folder with the name size of test001.thn

RemoteServer.dll+249B1 0x19F549B1

8B 36 8B 7D 38 8B C8 8B D1 C1 E9 02 ->
8B 36 BF 21 9A 30 06 FF D7 C1 E9 02 

Common.dll+A9A21

90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 ->
BF 71 9B 30 06 89 7D 38 8B C8 8B D1 C3 90 90

@Gold_Sear Sorry for the radio silence on this, I’ve been otherwise engaged! I’ve accepted your PR and fixed a few syntax issues with the merge. Hopefully will have some time this evening to make a push and finish off a few more sections.

@Groshyr It just adds external equipment to the types it tests; perhaps have a look at the original request (last paragraph of that post, plus most of the rest).

@IrateRedKite No worries, I’ve been away too.
goes back hunting for solutions on his list

@josbyte,@adoxa: added your offset to the payload and to KraftFragment;
@Venemon : added your offsets to the payload and KraftFragment, with the exception of #7, which was already found by adoxa in 2010.
goes off testing the new patches

Hello everyone I got some crash feedback about some of my offsets, I suggest removing them

1.Auto-CM without activation (crashes with wrecks)
2.Guided projectiles wont give up tracking a target(effects everything in unintentional way)

for the first one, everyone should use BC46’s alternative
and second one here is a better alternative

server.dll+1460C
This will allow 360* FOV missiles and as a side effect, missiles will not give up chasing their targets, if it is 360*FOV

(seeker_fov_deg = 180 means 360* FOV)

0F 8A ED 01 00 00 -> 90 90 90 90 90 90

(as technical note, normally missiles cannot have fov above 180+ due to a limiter that checks missile's trajectory against a target, if it is negative, it kills the seeker)

Just adding this one here too, that is discovered recently

Freelancer.exe+F8C36
Alchemy will read "-1.0" engine state
this will allow -1.0 ALE effects to spawn for reverse impulsing

7A 16 -> EB 16

@Venemon I think with these adding an adjustment to the post with a disclaimer saying that these crash and recommending the alternative offset might be the way to go, as these addresses are potentially useful for additional reverse engineering!

The list:

HUD
Miscellaneous
Missions
NPCs
Reputation
Server Operation
Systems
Turret View and Mouse
Visibility
Visual Effects

Having gone over this category list and checking offsets within each page against the json, we seem to be done! I added a few extras from Visibility, and need to comb recent activity in this thread to make sure there’s nothing new I’ve missed, but we’re nearly ready to do a category/accuracy pass and retire the old page I think!

I’m tracking issues with a few offsets here: https://github.com/TheStarport/StarportDocusaurus/issues/12 so if there’s any that need adjustment/investigation and it’s not a straightforward fix, please add to the issue

IrateRedKite created this issue in TheStarport/StarportDocusaurus

open Offsets that need modifying/format adjustments before being added to the Limit Breaking 101 Page #12