Dev's Limit Breaking 101 Techniques

adoxa

@Fox: remoteserver.dll has the last ‘l’ chopped off. I would also like to see a constant six digits for the offset (and no 0x prefix).

foxUnit01

Noted on both counts. I agree the 0x is annoying as you can’t double-click the offsets to select them for copy/paste, but instead must manually highlight, so I’ll take those out and use a constant six digits on the offsets. Also, the last l was chopped off to keep the tab-delimited table from going screwy; considering remoteserver.dll was the only culprit, I figured it really didn’t matter much.

Any other suggestions for the list? Any offsets it’s missing? Also, do you like the new organization? I’m thinking about going through and reorganizing the wiki to match the new list (and add in any missing offsets to it)

Edit: Oh, and still think I should get rid of the 1.0 offsets?

Bullwinkle

foxUnit01 wrote:

I agree the 0x is annoying as you can’t double-click the offsets to select them for copy/paste

Edit: Oh, and still think I should get rid of the 1.0 offsets?

Thank you! Please make sure that you terminate the offset so that copy and paste actually work correctly.
I am glad that you keep asking about 1.0 offsets, FoxUnit01. Because I cannot figure out who would want them. Ever.

But that’s just me.

(Maybe you could archive the 1.0 list as it stands now, and focus on 1.1 offsets for the future?)

Gisteron

what about, if hack requests, come up, the findings are uploaded to the list rather than to the topic, and the topic would point to it either by post or by script (kinda, any time a certain name string called hack request or such is in the name). so, no offsets would be missing spread out the forum but all stored in the wiki.

foxUnit01

The wiki is already linked in the first post of the topic. As for the stand-alone list, I maintain that because I feel keeping a portable and easily downloadable version is a valuable resource.

w0dk4

replace 6 bytes with 0x90 in freelancer.exe, 0x158a14 =  remove 20 fps limit in menus when using low graphics settings ~w0dk4

adoxa

No need for a hack, it’s controlled by fps_20_cap & fps_30_cap in DATA\SCRIPTS\rtcslider.ini. The Peformance Detail slider is a value between 0.0 and 1.0:

float RtcSlider::get_fps_cap()
{
  // Ignoring all the testing, assuming set_less.
  if (detail < fps_20_cap)
    return 20;
  if (detail < fps_30_cap)
    return 30;
  return 200;
}

M1C

return 200;

This looks like the max-value, is it increasable?

MfG
M!C

adoxa

What, 200 frames per second not enough?

common.dll	01A74C	200f = maximum FPS PART 1 ~adoxa
common.dll	01A892	2CB239->0x4CA727 = maximum FPS PART 2 ~adoxa

foxUnit01

07/14/10:
– Added adoxa’s radiation offsets for CloakingDevices
– Added adoxa’s repair offsets for items with ids_name = 0
– Completely reformatted the list, axing the 1.0 offsets and removing the 0x before every hex value to make the list more efficient

Sorry it took so long to do this, things have been busy as of late - I’ve probably missed recent other hacks as well. I’ll take a look around later.

Edit: lol, one right on this page

foxUnit01

Updated the wiki in full. All new offsets were added, organization was overhauled to match the list, and ConTEXT screwed up the little arrow symbol.

Some of the hex-overwrite hacks were really really long, and I wasn’t sure what to do about them other than break them up into multiple lines; I’ll leave that for someone more wiki-experienced to figure out.

w0dk4

nice job

foxUnit01

– Indexed adoxa’s NPC scanner (enables CM usage) offset
– Indexed adoxa’s wireframe flashing fix for hit_pts = 0 items
Committed these to the wiki as well.

Edit: Oops forgot the maximum FPS offset, that’s in there too

Vital

1.1 content.dll c2946 5000 longint = distance from the player below wich npc spawning at tradelane ring is rejected(spawning is transfered to the next ring)~Vital

adoxa

@Fox: Here’s a reprint of a few you haven’t indexed. I haven’t included the wireframe equipment one.

common.dll	0E698E	7C->EB = some planets keep on spinning ~adoxa

freelancer.exe	1D8D08	1500f = maximum distance to initiate trade ~adoxa

common.dll	0D670F	C644243001->E947FFFFFF = suns will honor visit flag ~adoxa

foxUnit01

Thanks, I’ll put those in. I was bookmarking posts containing offsets for a while, but now that bookmark tab is huge and needs to be cleaned, so I lose track pretty easily.

Edit: Done. Now to resist heating up pizza instead of going to sleep; it’s almost 5AM after all…

adoxa

Yeah, I’ve started keeping them myself, so I don’t have to go searching before you index.

Heh, your almost 5am is my almost 7pm. It’s now just shy of 2am here, and I’m off to bed.

Sethernis

For those who don’t use FLHook, I think this should be added to the list:

server.dll 3A068 8b = maximum group size PART 1  ~Unknown

server.dll 3A46E 8b = maximum group size PART 2 ~Unknown

I found the offsets in FLHook’s hook.h.

foxUnit01

adoxa wrote:
Heh, your almost 5am is my almost 7pm. It’s now just shy of 2am here, and I’m off to bed.

I have a friend over in Melbourne I communicate with fairly regularly. YOU’RE FROM THE FUTURE.

And, uhh, right, I’ll get those group offsets in the list.

adoxa

Syd wrote:
Is there a way to aktivate the collisiondetection on Server for NPCs and Loot and so on?

Well, I don’t know about the veracity of this method, but here’s a patch that disables turning collision detection off (for everything). If it works (or even if it doesn’t), I’ll at least have a starting point, but it’ll be quite some time before I have a proper look.

common.dll	0258EB	8B4C24086A0151->6A016A01909090 = always enable collisions ~adoxa