I now added Crash Offsets to KraftFragment, sorted by offset.

@adoxa : Thanks for having a look. Added to my list.

I was hoping @adoxa would have a look at this, as he’s usually very fast at figuring out these kind of things. If not, I’ll add it to my to do list.

I’ve applied all nine patches and installed the two plugins, still can’t reproduce the error. Two more things to try:

• Replay the story after deleting restart.fl with the patches and plugins applied, and
• Install this HD mod @CommanderArgelo uses. Where can I find it and what do I need to set up to make an adequate testing environment?

Thanks, will test it out tomorrow.

So I applied all of the above patches (and even increased some of the ranges) but none of them reproduced the error.
So, @CommanderArgelo are you using any plugins in your mod?

Thanks for sharing, will test it out later.

Which offsets from the 101 list are changed in your mod?

Since Act_Invulnerable is used in other places durring the story as well, you might encounter the bug further down the story, while this effect definitely isn’t there in Vanilla, so you may have caught an unforseen side-effect of some offset from the 101 list, or a plugin.

Do you use any plugins in your mod?

I’m also curious as to what causes this bug. This happens in vanilla too?
What happens if you remove the line Act_Invulnerable = PEscort1, true, false, 0.9 from the [Trigger] convoyapproach_init in m02.ini?

Major update: points 6 and 8 are resolved! See also here why this is important.

Found it! It took me quite a while as usual, but now points 6 and 8 of my to do list are solved!
Here are the results:
Point 8 was solved a few posts above; this is in addition:

#add vertical component to random spawn
#Gold_Sear, 31 January 2025
File: content.dll
C1F0B: 4C E4 14 C1 E9 07 EB 03 [ 0C C2 8B 7C C2 04 C1 E1 ]

Point 6 (the first one is just as illustration, already exists):

#distance from player position at spawn moment that an NPC patrol with arrival = cruise will fly to when spawned
#M0tah
#Gold_Sear, 18 January 2015
C4C01: 500f #min
C4C06: 2000f #max
|-
#use spawn position instead of player position for arrival = cruise (allows to safely increase spawn distances)
#Gold_Sear, 27 January 2025
File: content.dll
C2011: 45 00 EB 02 [ 84 24 1C 0D ]
C2022: 45 04 EB 02 [ 84 24 14 0D ]
C2034: 45 08 EB 02 [ 84 24 18 0D ]

Hi folks! I’m on my way to cross off another point of my list. I’ll post some intermediate results:

#min distance between waypoints for behavior = wander
#Gold_Sear, 6 January 2025
File: content.dll
118114: 1500f
|-
#max distance between waypoints for behavior = wander
#Gold_Sear, 6 January 2025
File: content.dll
118118: 3000f
|-
#randomize flight direction for behavior = wander
#Gold_Sear, 6 January 2025
File: content.dll
C14EB: B9 D5 FF FF FF F7 F9 [ 8D 14 33 83 C6 0C 4D ]
C1508: 8D 14 33 8D 34 86 D9 C0 D8 4E EC 4D F7 D8 EB 05 90 [ D8 4E EC D9 C1 D8 4E F0 D9 5C 24 24 D9 C9 D8 4E F4 ]
C1520: 1A D8 4E F0 D8 47 C4 D9 5A 04 D8 4E F4 D8 47 08 D9 5A 08 8D 34 86 83 C6 0C 85 ED EB 10 [ 5C 24 14 D9 44 24 24 8B 44 24 14 D8 47 04 D9 5C 24 18 D9 44 24 28 8B 4C 24 18 D8 47 08 ]

I’ll put everything on KraftFragment once the entire point has been resolved.

@IrateRedKite : do I need to provide Google account details?

I know it’s a bit late, but count me in on this project. I won’t be able to work on it every single day, however. Did have a plan to work through the archive some time ago, so this will be a good ‘stick behind the door’.

@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

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

@Laz: thanks again for fixing my typos!
@self: remember to turn off the ‘insert’ button and fix it’s damage!

EDIT:

#make accounts less vulnerable to crashes due to too many cargo/base_cargo lines in character files
#double the size of Freelancer's 'visit' packet (MP only)
#Jolly_Roger, 14 September 2012
#adoxa, 7 March 2021
#adoxa, 1 October 2022
File: RemoteClient.dll
96B1: D0 27 [ 00 28 ]
96E8: 30 20 03 [ 00 90 01 ]
9707: 20 03 [ 90 01 ]
File: remoteserver.dll
9AE5: D0 27 [ 00 28 ]

This patch is actually a composition of two patches that alter the same code, hence had to be merged.

#colors of several things hardcoded in freelancer.exe
#adoxa, 7 January 2010
File: Freelancer.exe
0bd8ec: 43 # R of tooltip background
0bd8f1: 61 # G
0bd8f6: 70 # B
0bd933: b9 # R of tooltip text
0bd938: f7 # G
0bd90b: ff # B (this is e0 of an unused color)
0bd92a: 0f # change it from 0e so above works
15b22c: ff # R of selected maneuver icon
15b231: ff # G
15b236: 00 # B
15b2cb: ff # R of selected neural net icon
15b2d0: ff # G
15b2d5: 00 # B
15b2f6: ff # A of both
161be6: 87 # R of main text color (aqua)
161bed: c3 # G
161bf4: e0 # B
161bfb: c0 # A
161c06: 87 # R of main color (aqua)
161c0d: c3 # G
161c14: e0 # B
161c1b: ff # A
161c66: f5 # R of selected color (yellow)
161c6d: ea # G
161c74: 52 # B
161c7b: ff # A
161ce1: 80 # RGB of disabled icons
161cf7: ff # A
199da6: 87 c3 e0 # RGB of some buttons
199dab: 87 c3 e0 # and again
199dc6: 80 80 80 # RGB of disabled buttons
199dcb: 80 80 80 # and again

Probably want to make a new section ‘HUD: Colors’ to add it in.

EDIT: indexed to payload.

Ah… I did make a typo (thanks Laz!)

Okay, so I’ve gone through my archive of untested offsets, found quite a few:

• from this thread the following, tested:

#camera of target wireframe on the top (like a playership wireframe)
#Jeider, 9 April 2020
File: Freelancer.exe
E3D09: B1 01 90 [ 0F 95 C1 ]

#always show target wireframe
#WhiskasTM, 29 July 2019
File: Freelancer.exe
CFE75: 00 [ 01 ]
E203E: 90 E9 [ 0F 84 ]
E20FF: EB [ 74 ]
E3CE0: 90 90 90 90 90 90 [ 0F 85 8F 02 00 00 ]
E1F91: 90 90 [ 74 60 ]
E36DA: 30 [ 08 ]

#force 1st weapon group to be set on entering space
#WhiskasTM, 29 July 2019
File: Freelancer.exe
DB6A5: 07 [ 13 ]
DB6B7: 6A 00 [ EB 05 ]

#make target wireframe ignore all mouse events
#WhiskasTM, 12 July 2019
File: Freelancer.exe
E7DF9: 30 C0 [ B0 01 ]

From here:

#steering arrows always go to mouse
#adoxa, 2 May 2010
File: Freelancer.exe
C8864: EB [ 75 ]

#increase to 12 steering arrows
#adoxa, 2 May 2010
File: Freelancer.exe
C885B: F8 1A 48 [ DC 75 5C ]
C886A: 1.8f [ 1.0f ]

#distance between steering arrows
#adoxa, 2 May 2010
File: Freelancer.exe
C8AE0: 74 86 4C [ DC 6E 5D ]
C8674: 0.15f [ 90 90 90 90 ]

#size multiplier for steering arrows
#adoxa, 2 May 2010
File: Freelancer.exe
C8A6F: 78 86 4C [ E0 75 5C ]
C8678: 0.5f [ 90 90 90 90 ]

Furthermore, I dug up two offsets of my own that I never published:

#hostile threshold for Closest Enemy
#Gold_Sear, 6 June 2024
File: common.dll
13E548: -0.6f

#max selection distance
#Gold_Sear, 6 June 2024
File: Freelancer.exe
1DC130: 10000000f

Everything added to the payload, including fixes for bugs I made earlier.

EDIT: done. I forgot to mention that there are untested patches by adoxa to make NPCs on server recognise collisions. However, since I am unable to test multiplayer-related stuff, I can not test them right now. Someone else willing to?

@Laz: thanks!

Meanwhile I’ve added the ‘Systems’ section, naming it as is.

EDIT: the sync seems to be lost again: where did I make a typo?

EDIT2/Update: also added the ‘VFX’ section. I recall having some more offsets laying around, haven’t tested them yet, will add them soon.

I’ve powered through and also added the ‘Turret View/Mouse’ section (renamed to simply ‘Turret View’, as all the offsets are focused on that). Also added a timestamp I forgot in the ‘Display’ section.