What is the crowd's opinion of Hex Workshop?

From 3.5 billion comments

One thing I've not seen here is a good hex editor for the firmware, raw data, and reverse engineers. I know it's a little expensive, but Hex Workshop is so worth it. One of these days I'm sure they'll be eclipsed by open source stuff like rehex ... But not yet.

http://www.hexworkshop.com/

hex edit minecraft.exe and change 1.14 to 1.12 and u will be able to connect

http://www.hexworkshop.com/

​

if you change it to 1.12.3 u also bypass queue server but don't tell hause

Download an Hex Editor (http://www.hexworkshop.com/)

After installation, right click your Borderlands2(.exe) and choose "Hex Edit with Hex Workshop" https://i.imgur.com/w76pNvx.png

Lots of numbers will appear on the screen but the rest is simple.

Use the CTRL + H thing again and find 83 C4 0C 85 C0 75 1A 6A

You replace those numbers with 83 C4 0C 85 FF 75 1A 6A

Next you find 73 00 61 00 79 00 and replace with 00 00 00 00 00 00 and you save.

Now your mods should work again.

I yoinked this content from someone else

Is this an .exe file or something like .bat/.cmd?

If the former, you could try opening it with Hex Workshop and search for the things you wanna change, if they're in plaintext that should be easy. Note though that you cannot increase the length of the texts. Try replacing it with something of the same length or fill up with spaces if your replacement is shorter.

If it's a bat/cmd file, you can do this with notepad.

> They are saved as PNG, so I can't directly compare the file data.

You can. Like I said, you can "open them all in a hex editor...and do a file compare." I use Hex Workshop, but there are plenty of other options out there, too. This would enable you to see if there is absolutely any difference with these files at the byte level. Even a PNG can be saving different information in its header area, and there are actually multiple ways to store the same PNG data. (This is like a 5-minute test, compared to your other which takes longer to carry out, so I would always do the quickest and easiest test first when debugging!)