Dev's Limit Breaking 101 Techniques

foxUnit01

Hey folks, updated the topic and uploaded a new version to http://www.memes.no/88flak/downloads/beta/1.0-1.1_Offsets.txt

This list needs to be reformatted badly. I’ll probably work on that today.

Edit: More stuff and threw a lot of adoxa’s stuff I found into Unfinished because it’s big and I’m lazy so I’ll index it after dinner.

tai

What about the wiki page I created? Why don’t you use that as a starting point for redoing the list?

w0dk4

Wiki Page: http://the-starport.net/freelancer/wiki/index.php/Limit_Breaking_101

foxUnit01

Personally, I prefer the list in a text document format for portability and ease of editing (I think the new list isn’t too shabby - http://www.memes.no/88flak/downloads/beta/1.0-1.1_Offsets.txt ), but I’ll update the wiki as well.

adoxa

Well, that stuff of mine (colors) doesn’t really need to be added, since you could just use the Tiny Hexer script to do it. And it’s hexadecimal. Is it really necessary to persist with the 1.0 offsets?

w0dk4

I think we should scrap 1.0 offsets alltogether, no reason for anybody to use v1.0 dlls/exe.

OutCast

Well, they could still be useful for those who don’t want to include 1.1 patch in their client mod. I see your point, though.

foxUnit01

I’d prefer to keep the 1.0 offsets simply because that’s a lot of data going to waste otherwise. However, I suppose a lot of the new (and damn useful) offsets found don’t have 1.0 offsets, so maybe it’d be better for the sake of cleaning the list.

Also, any opinions on the new text list?

M1C

Syd wrote:
yes, but I dont want to use it on a normal Server.
I need it for a Event-Mod - and there are no NPCs needed, just 1 loot. And I think 1 little object cant overload a Server.

Is this possible?

MfG
M!C

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.