Dev's Limit Breaking 101 Techniques
-
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.
-
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?
-
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?
-
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?)
-
-
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.
-
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; }
-
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 efficientSorry 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
-
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.