Dev's Limit Breaking 101 Techniques

@Gold_Sear Sorry I’ve been absent, was moving house! I’ll see about doing a pass on this tonight and at least making a list of sections that still need work if I can’t get the scripts working properly to generate the page.

I’ve also come across RL; finally updated KraftFragment.
@IrateRedKite : good to see you back!

Sorry for the long delay, it’s been a busy few weeks and I got a bit caught up in some FLHook stuff which ended up eating way more free time than I thought it would.

Sections that still need doing are:

HUD
Miscellaneous
Missions
NPCs
Reputation
Server Operation
Systems
Turret View and Mouse
Visibility
Visual Effects

Going to get a couple of these done this afternoon, and will edit my post to cross them off the list.

@IrateRedKite Visibility is done

@Gold_Sear Fantastic! I’ve crossed it off the list.

@Laz has kindly put together a demo page where the json payload will render (this will eventually move to where the main page is when it’s done) so we can see how things will look when finished.

You can find it here: https://the-starport.com/wiki/fl-binaries/limit-breaking-v2/

@IrateRedKite I added some more offsets to the payload, as well as additional URLs of already added ones and updates/bug fixes.
Since some of the offsets (eg the max credits in MP) date from the lancersreactor.com era, could you perhaps please re-activate the search function over there? I’ve managed to find the original Limit Breaking 101 topic but not much more.

@Gold_Sear I’m afraid since it’s been converted to a static html site, that is no longer possible. However it should have been indexed by Google now. Try something like: site:lancersreactor.com test

@Raikkonen thanks, that should work too

I added some more stuff to the json payload. No new sections, just some extra offsets and URLs, as well as bug fixes.
Also, I restored the offset format as in the old Limit Breaking 101, as adoxa requested back in the day, to make copy-pasting the offsets easier.
@IrateRedKite Permission to do this for all offsets please.

@Gold_Sear Thanks for the additions!

Don’t change the format in the JSON payload right now, what we can do is set up a filter that lets you toggle between the 0x format and the one that just lists out the address so we can make sure any leading zeros are added as appropriate on the final page without a bunch of extra work. I think it’s okay to leave your PR as it is though. I don’t think it will mess up any parsing!

@IrateRedKite ah, thanks, just did some bug fixes from my part that need to be pulled aswell

EDIT: will revert it in the next commit

An update: I did some work on the ‘equipment’ section (mostly).

While underway, I simultaneously edit KraftFragment to BwPatch format, will be updated once I’ve gone over the entire list.

@BC46 said in Dev's Limit Breaking 101 Techniques:

Show all group members on the nav map:

Freelancer.exe, 08DC07, 
E9 85 FD FF FF 90 90 90 -> 83 C5 18 E9 82 FD FF FF

Update:
When I came up with this patch, there was one thing I overlooked. If you had one or more group members that were docked at a base, the original problem would still partially occur.

If anyone has applied this patch already, please undo it and apply these instead:

Freelancer.exe, 08D89B, 90 90 90 90 90 -> 83 C5 18 EB 50
Freelancer.exe, 08D997, 55 -> 00

Now it should work as intended.

I’ve powered through and completed the HUD section on the new limit breaking in it’s entirety, may get another chunk done this afternoon. I think I may also do a pass of this thread again and ensure any new offsets are added to the new page if they’re not already present.

@IrateRedKite Nice! Check’m out later.

Meanwhile, I’m currently working on the ‘NPCs’ section (formerly NPC Spawning and NPC Behavior sections).

Update: I added the rest of the NPCs section to the payload, so that section can be crossed off.

@Gold_Sear Excellent work! I’m going to look at making sure Missions are done tonight.

We’re going to make an update to the page generation script for these. I’ve scoped a little issue to keep track of what needs doing. If there’s anything in addition to what’s in the comment here, please let me know and I’ll do what I can to get it added: https://github.com/TheStarport/KnowledgeBase/issues/39

IrateRedKite created this issue in TheStarport/KnowledgeBase

closed Convert limit breaking to json #8

I’ve added the ‘Server Operation’ section to the payload.

@IrateRedKite you mentioned in your last post that timestamps should only show the date. My timestamps are accurate up to the minute (as most posts have this accuracy in their post date). Is this a problem?

@Gold_Sear Brill! I’ll cross it off the list. As we’re using unix timestamps here, it’s not a problem at all, we just need to adjust what the script that creates the page displays. If we change our mind in the future we can simply adjust the script and display the down-to-the-minute times again

I’ve added every URL and timestamp I could find on the former ‘Misc’ section. In this search for URLs I noticed that some of the offsets were miscredited, e.g.

• “don’t show the unknown graphics card warning” was already found by OutCast in 2011; and
• “Name of folder where FLSpew.txt is stored” is actually found by HeIIoween in 2015.

@IrateRedKite I like your recategorization of the Misc section However, we now have an ‘equipment’ section and an ‘Equipment’ section which are actually distinct. Also, the sync between the payload and Laz’s page seems to be lost, is this indeed the case?