• Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
  • We've added LLM sections to our Terms & Rules and Resource Rules, for everyone's sanity & in-game safety.
    Read more
    a. Do not replace your voice with an LLM. This goes for your posts and your scripts. Drafting and editing with a tool is fine, but don't take you out of what you share.
    b. Do not replace your EQ character's voice with an LLM. We don't want scripts that speak over /ooc, /shout or other public channels. This has been an unwritten rule that's kept casino scripts off the site for decades, but we're now compelled to make it clear: keep automated communication private.

    Why Does RG Review Scripts?
    Nearly every LLM-written Lua script we see is making your character do impossible things, and rarely in a way that's beneficial to you. We've seen heavy server hammering, /target over impossible distances when /nav spawn would passively accomplish the same thing, a spawn search that fires 20+ times per second, and other pointless actions that are likely annoying GMs.

    You are welcome to use LLMs as a tool to structure, draft, and edit your work, but please read critically before hitting /lua run

DoCrack ini merge utility

Destro

Member
This isn't anything earth shattering, but I thought I would give a little back to the community. Because I'm lazy, I don't want to see every crack under the sun when I'm using DoCrack. So I trim my personal INI file down to just what I want to use. So rather then having to do a bunch of copy paste when a new batch of offsets comes out, I just run this utility to merge in any changes.

It's probably not perfect, but it does the job for me. It sorts the cracks alphabetically as a side effect. Feel free to kick the tires. If it's popular enough I'd be willing to release bug fixes and add features. If nobody cares, then eh, no worries. :cool:

The only requirement is you'll need access to a perl interpreter.
 
Last edited by a moderator:
I should have mentioned how to use it. Just copy / paste the entire new post of offsets into some file and save it in the same directory as your MQ2DoCrack.ini file. Save the patchDoCrack.pl in the same directory. Then just run the utility feeding in the name of the new crack file. It will merge things with your current MQ2DoCrack.ini and output a report of what it did. The patched ini file will be saved in the same directory as MQ2DoCrackPatched.ini. If your happy with the changes, manually copy the MQ2DoCrackPatched.ini over the top of MQ2DoCrack.ini.
 
Fixed up a few problems I found, details are inside the file. Does anyone know if the components which make up each crack are case sensative? Things like crack0, address0, normal0, Description, DefaultSetting, etc?
 
i am a little confused.... so let me try and tell me if i am wrong

you will copy and paste new offsets into a new file

then run this and it will put the newer offsets into the docrack.ini

BUT it will leave any offsets that have not been replaced?

and it will make them alphabetical?






if all thats true.. aren't you setting yourself up for a CTD? old offsets and such...

if your gonna C/P the offsets anyways.. why not just open docrack.ini -> Ctrl-A-> Ctrl-V





I am curious... not baggin on your work ... its some good stuff...

also notice some who start docrack threads are posting in alphabetical order.. for ease of finding cracks.. 8-)
 
Army, your correct. As it stands right now it leaves the old offsets if it has nothing to update them with. Is there a comment character? ie "#" I could use? If so I'd like to have it auto comment them out, and when a newer offset is found have it remove the comment and update the crack section. If not I'm thinking I may just have it automatically add/override the DefaultSetting and flip it to "off" as a semi safeguard. Another thing I could do is split them off into a seperate holding file, just to keep track of them until a good offset if found. I'm just not all that familiar with the rules DoCrack uses when parsing it's ini files. That's why I was also curious as to if it's case sensative on the keywords used to make up the crack information. Right now I'm just putting this out there to see if there is enough interest for me to flush it out into a full blown utility. No sense in putting a lot of effort into it if there isn't much of a market for it.

The main reason I wrote this was for people who wanted to keep a trimmed down version of their INI file and want a quick hassle free way to update it. It uses the crack sections in your current ini as a guide and updates them from the massive DoCrack.ini which is usually posted. For me it makes the in game UI easier to deal with. I find about 70% of the stuff listed in the big ini file, I don't want.
 
I actually store each DoCrack INI in individual INI files, each files just called the same as the DoCrack offset.
Then I just run this command to get all that have the correct date, and merge them into MQ2DoCrak.ini:

Rich (BB code):
grep -l "2005.10.27" * | xargs cat | cat >> ..\MQ2DoCrack.ini
 
DoCrack ini merge utility

Users who are viewing this thread

Back
Top
Cart