Hacking [Request] Better GBA cheat for EZ-Flash Omega

[DeadSkullzJr]

Gotcha. May I ask, what letter have you made it up to since your last update?

I no longer go based on letter anymore, and instead go by No-Intro numbering, and the reason being is because the database logic EZ-FLASH team went with uses a numbering system alongside the game identifiers, I realized that how I was going about the entries wasn't very viable in the long term due to the fact many entries exist alphabetically but aren't actually listed in many places of the internet, not to mention EZ-FLASH doesn't have a number system that I can use to determine what numbers go to what entry for any that I add that didn't exist before in their database. Considering the goal is to build a rough base for people to start with for the first release, the only logic that makes the most sense is a numbering system that doesn't really change (at least not for the much earlier numbered entries, later releases will have to be accounted for when that point is reached), No-Intro's numbering logic is currently viable enough to work with, this change won't restrict me alphabetically either. As such, the database is no longer able to be determined based on letter anymore, and is now only able to be determined by how many entries exist. One downside however, I had to redo some things recently due to having to get Windows reinstalled a couple times due to some issues I was facing in both instances, so it set me back a little bit (lost some stuff too by collateral), but I've been playing catch up to get it back to where it was before the issues.

 

[Absarck]

Hi! Just wanted to ask how progress has been on this?

Post automatically merged: Apr 17, 2024

Hi! Just wanted to ask how progress has been on this?

 

[DeadSkullzJr]

Hello everyone, I meant to mention this about a week ago, but I ended up busy. A lot has happened during my time with this project, some of my previous work has been scrapped in favor of something newer and better than before, real life stuff, had to do some level of recovery as I did lose some things during my time dealing with an operating system reinstall process, and have also been dabbling with other fields of interest (videography currently), I'm happy to say that so far I'm a little over 900 entries in (no particular order since I changed the way I handle things now). I still need to tune up many of the entries, include more codes, etc., but so far a base of release is definitely becoming a reality. I know it has been quite a long while now, but it's coming together. I'm sure to most a little over 900 entries doesn't seem like a lot within the time frame I've been working, unfortunately scrapping and recovering data tends to do a bit of a number on the final results.

Some general good news though maybe some pointless details here and there, some of which that ties in with the projects, my work environment has improved slowly but surely. Unfortunately some of my fields of interests are demanding on hardware requirements, I now pack more memory (great for multitasking in general) and have some more drives for storage (need it since some of my interests are also storage hogs), the machine in question is six years old now (turns seven in two days), still packing a mean punch with the tasks I perform with it, but with the development cycle of software and such, sadly all it takes is ONE update to essentially kill your capabilities, unless you sit behind (which is fine, but it isn't always optimal). This is partly why I tend to go my own path and get inventive, create my own solutions to get what I want done, etc.. Considering this though, I have been thinking about building a second machine in the future for the much more demanding tasks, especially the tasks that take hours to do (video encoding and such for example), so I can continue working on projects like these whilst the other machine is doing whatever heavy tasks I need it to do at the same time. I also decided to swap to an ergonomic mouse, considering the amount of work I do, a normal mouse isn't very good for wrists, even with a mouse pad with a built-in wrist pad. Again, likely some pointless details, but for me, they are important improvements that help keep me going. I'm trying to avoid an upgrade like the plague considering the current state of technology is.... suboptimal to say the least, so much power yet very inefficient every other way, I certainly don't like that motherboards are now popping up with less PCI-E slots and such to work with (most keep fancying the damn NVMe stuff, it's getting kind of annoying when that is sort of kicking other potential board features to the curb), not to mention the concerning levels of issues with how they handle processor clock speeds, power draw, etc., don't even get me started with the space heater graphics cards that basically act as fireplaces in the winter, all around a disappointing scene for the computer side of things thus far. I would rather sit and make a second system that's generations behind if I have to, at least I'll know it won't explode, cause summer to exist in December, or drive up the electricity bill like crazy (who am I kidding, it would likely burn up and incinerate in my hands if I had it in the same room as the furnace computers of today).

Anyways, if you made it up to this point, thanks for reading, hopefully I at least put half a smile on your face, and I hope to have more progress to talk about later.

 

[rand92000]

Hello everyone, I meant to mention (...)

Hey. Thanks for that you're doing it and we all know you're having your life and all but I wonder about 2 things:
1. How would we easily know it got released when it will? Like... will you edit your first message so it was easily visible? Or redirect us to your github or something...? (Idk) I'm asking because I was browsing all the topic for 10 minutes just to find out it's still not ready yet. Would be nice to know that it will be instantly visible information, yk.
2. I also wonder... Instead of releasing it all at once in a bulk, couldn't you just upload what's already done and checked and do monthly or even quarterly updates of the newly finished content to be added for your project? Just to give us access to 'something' that we're waiting faithfully from over 6 years. Couldn't it be handled such way instead? Through releases with updates?

Please don't feel rushed by those questions, I just simply wish to know.

 

[DeadSkullzJr]

Hey. Thanks for that you're doing it and we all know you're having your life and all but I wonder about 2 things:
1. How would we easily know it got released when it will? Like... will you edit your first message so it was easily visible? Or redirect us to your github or something...? (Idk) I'm asking because I was browsing all the topic for 10 minutes just to find out it's still not ready yet. Would be nice to know that it will be instantly visible information, yk.
2. I also wonder... Instead of releasing it all at once in a bulk, couldn't you just upload what's already done and checked and do monthly or even quarterly updates of the newly finished content to be added for your project? Just to give us access to 'something' that we're waiting faithfully from over 6 years. Couldn't it be handled such way instead? Through releases with updates?

Please don't feel rushed by those questions, I just simply wish to know.

1. I will likely make my own topic about the database when it comes out, much like I did with my NDS(i) databases. You'll know, and you'll have something that can be bookmarked for later.

2. This is a multi-step operation, it's a bit of a hassle having to constantly prepare updates just to get back to work and prepare all over again. I don't work on the databases every single day since I have an outside life, so I can't even guarantee short burst updates either. I work at my own pace and manage my time with these things, that way I don't pull my hair out. There's a trade off to be considered:

Option #1: Short Burst Updates
- Time crunching.
- Potential focus on things that may not be as important (the database in this case) over more important things like a job, college, etc. (basically something that shouldn't ever be done). Let's just set this one aside though for other points.
- Buggy releases, no update is without its potential problems, but anything in short bursts tends to be its own kind of rush. It's a rush to try and cram content just to fit the bill for a potential release, then having to plot what to do next right on a dime in these short burst intervals. A monthly release seems like enough time to do stuff, but when you have a lot going on in between, it isn't as much as it sounds or seems. Maybe if one has a ton of free time this could be viable.
- The hassle of having to perform constant updates on the user's end. Updates are great, but having to perform updates constantly is a hassle. Personally I'm a firm believer that larger updates are better, why, because they may not come out as often, but when they come, they contain a lot of fixes as well as new contents. Nobody has to dread "yet another update" when it isn't often they perform them to begin with.
- Burnout. Burnout sucks, doesn't feel great, short burst updates can lead to burnout quite easily.

Option #2: Paced Updates
- No hair is being pulled out.
- Dedicated focus for each task so nothing important is interfered with.
- Paced timing, so one can get to these projects with ease.
- Far less buggy releases.
- Longer wait times, but the balance here is larger content updates.
- No burnouts.
- No constant update hassles, one gets an update, they can enjoy it for a while. Spend more time playing rather than having to worry about updates constantly in this case.

 

[rand92000]

1. I will likely make my own topic (...)

Option 2 sounds nice imo. That's kinda what I meant to suggest.