Dev's Limit Breaking 101 Techniques

[c]13DF88[/c] in [c]common.dll[/c] is used by a lot of things - I strongly discourage modifying it.

foxUnit01 wrote:
Added note to Gold_Sear’s multiplier for min cruise speed in formation, as this hack seems to bork up asteroid fields

Thanks for the heads up. Didn’t notice that one.

On that note though, do you remember how you found the multiplier for min cruise speed in formation?

Since I’m not a pro reverse engineer like adoxa, I found this one (and most of my offsets) through trial and error (yeah I know…). Only thing I knew was the value to look for.

For example I found this one

Gold_Sear wrote:
Freelancer.exe 1D8D08 1500f distance over which non-selected arrows of important contacts on the edge of the screen start fading (note: same offset as adoxa’s max trade initiate distance)

But I didn’t find the fade crossing distance to add to this 1500 to get the distance over which the arrow completely disappeares (around 2450 by default).

adoxa found new offset, thought I’d post it here:

adoxa wrote:

Freelancer.exe 08E46B 60->C0 = allow up to 256 trade lane rings ~adoxa

The exact value is an integer one byte earlier: 192 * number of prev_ring (or next_ring, or Archetype = Trade_Lane_Ring - 2 * tradelane_space_name).

Nice find adoxa 8-)

EDIT: adoxa found another important one:

adoxa wrote:

File: pilot_f_leg_m01.utf
0000D7: "9A5CFD0"       [ "809CF08" ]
000DF2: "809CF08"       [ "9A5CFD0" ]

This fixes a bug that causes NPC’s to call Border Station Pirna in Dresden incorrectly by the Hessians base Vogtland (and vice versa, if I remember correctly).

fox, add this offset by M0tah to the list.

Greetings
goldsear

EDIT:
Change

In HUD:Limits:
freelancer.exe  D5984  7E->EB = remove speed display limit of 999 (alternative to above) ~Unknown
freelancer.exe  D5936  0F85->90E9 = remove cruise display limit of 300 ~Unknown
```to

In HUD:Limits:
freelancer.exe D5984 7E->EB = remove speed display limit of 999 (alternative to above) ~StoneD
freelancer.exe D5936 0F85->90E9 = remove cruise display limit of 300 ~StoneD

and add

freelancer.exe 1D7E80 300f = cruise speed display limit ~M0tah (note: same offset as Schmackbolzen’s tradelane waypoint reached distance)

greetings,
Gold_Sear

Good evening, old friends and perhaps soon-to-be new ones.

So, since I last saw this thread it has about tripled in length, and from what I gather some of the wiki page is out of date although there seems to be an effort of gathering and recovering all the offsets found in the recent years.
The particular one I am looking for seems to either not been found or not to be recoverable by search parameters I managed to intuit, so here goes.

I noticed at a velocity of about 1200 m/s and higher effects like space dust no longer render. I thought this was a matter of the ale, so I went in there and started coding away. Increasing emitter size, making effect alpha and size time-independent seemed, while otherwise making expected changes, not to break through what hitherto seemed to be an emergent limit. So my modder-senses tell me it must be hardcoded given that parameter any of the ini code seems to refer to is responsible.
Does anybody know this offset? And if it hasn’t been found, would someone versed with the appropriate tools and know-how kindly have a look for it?
And while we’re at it, what is responsible for the shaking during a system jump? it happens in both the target and the origin system irrespective of the properties of the tunnel. Is there perhaps a multiplier for that?
Many thanks!

Hi Gisteron

Assuming your question regarding the “shake” is about the screen shake:
I don´t think there is a way to prevent it for this particular event (jumping in or out of a system) but only for hull hits and shield hits.
Anyway… you can remove it completely.
Check out this offset:

freelancer.exe	11DB44	74->EB = remove screen shake altogether ~adoxa

Greetings
J.R.

I noticed at a velocity of about 1200 m/s and higher effects like space dust no longer render.

I expanded Manhattan’s atmosphere dust and changed cruise speed to 2500 m/s and that still seemed to be rendered.

And while we’re at it, what is responsible for the shaking during a system jump?

freelancer.exe	103E49	041F5D->3C3F50 = screen shake during jump PART 1 ~adoxa
freelancer.exe	103E7B	041F5D->3C3F50 = screen shake during jump PART 2 ~adoxa
freelancer.exe	103E8B	041F5D->3C3F50 = screen shake during jump PART 3 ~adoxa
freelancer.exe	103F3C	90909090->0.015f = screen shake during jump PART 4 ~adoxa

```(The original value is at 1D1F04, but that is used by other functions, so this moves it to 103F3C.)

Wow… another “FL-limit” that bites the dust…

@adoxa:
man… you´re simply AMAZING !!!
Thank you very much !!!

Greetings
J.R.

adoxa wrote:

I noticed at a velocity of about 1200 m/s and higher effects like space dust no longer render.

I expanded Manhattan’s atmosphere dust and changed cruise speed to 2500 m/s and that still seemed to be rendered.

Hmm, weird, the regular motion dust disappears completely. Maybe it is something in the ale after all, I shall compare it thusly with the atmosphere dust. Thanks for now…

[jump shake hack]

So many thanks! Still baffled how you do it but aren’t we lucky to have you goes off to bother someone else with his happiness

Maybe crazy question…

Does anyone know the distance for the aimbot to lock on the target crosshair?

What I mean is the following.
When hostiles come into fire range of your currently activated weapons, a small red dot appears at the screen, for any of the hostiles. You can move your mouse over them just fine, but when you shoot, within a small range of the red dot the fire direction ‘locks’ on the red dot, when there are two near each other it will lock on the nearest.

Does anyone know the offset to change this small range?

greetings,
Gold_Sear

Since this would be usable for cheating, there will be no answer to this question. Any answer will be summarily deleted.

FriendlyFire wrote:
Since this would be usable for cheating, there will be no answer to this question. Any answer will be summarily deleted.

<deleted some=“” text=“” here=“”>EDIT: since people are still playing FL online, I have to agree with FF, and I should read the rules better…</deleted>

I don’t care what you think, no answer will be allowed. I would recommend you don’t try to argue any further.

Far distances with this dot will lag your client.
Nice notice but i agree with FF - useless.

Considering weapon_equip.ini can be modified for cheating, then we don’t have to talk about it too… And about FreeLancer modding. Don’t be disappointed but this is strange.

If he modified any type of files, then, if he goes on a server, the flhook anticheat do the job very well, that’s really effective, tested many times with a few players. A server owner have to protect his playground against cheaters.

Why not have a try on this, the FL modding is an so vast and interesting subject

When i’m here i want to thank all the people on this topic, it helped me a lot from the past !

FLHook anticheat cannot detect those kinds of cheats. You really don’t know what you’re talking about, and it’s a bit irritating that you jump in this when I have clearly said that no answer will be allowed

weapon_equip.ini cheats are easy to detect
flhook, which should be running in every server meanwhile can detect them

other changes are not that easy to detect and it would be very hard for server admins to observe every file for possible changes

Im not saying that it is impossible since there clearly are methods to get that done but that would require all server owners to have alot of knowledge.

Some information is restricted for good reason. Accept it.

I’m very sure of what i’m talking about, it detects CRC of a given file and compares it with CRC in its configuration file, i’ve tested it a couple of times with a lot of file types dll, exe, ini, txt, works very well. When you modify a file it changes its CRC and the flhook anticheat will detect it (CRC cheat) and send the player with the modified file in a “prison” base.

That’s not so difficult to do, i can make a short tutorial about that. Servers admins have to know a bit. Anyway they are almost all empty.

Some information is restricted for good reason. Accept it.

And it’s very harmful for the rest of the modding community to keep these kind of knowledge. It’s like M$ who don’t want to release the FL source code.

Enough said, au revoir.

It’s like M$ who don’t want to release the FL source code.

And with this you demonstrate just how much you don’t know.

Nobody of that generation cheaters are actually playing this 13 year old dx8-based game that has neither cockpits, neither real size planets, neither realistic physics. Time is gone.

I don’t mind against roll & shoot / 90-flip & follow professional terminators, but to look at only, I hardly fight against current npc implementation even.