M3rein

The memeing remark was inappropriate, and I'm sorry for that. My tone was also rather hostile, but I stand by my comments beyond that.

Like you, @andracass, I'm not really interested in a long back-and-forth. I've responded to what I saw, and that's all I wanted to do. Whether or not you are making improvements, is none of my concern. Because as I mentioned, I'm certain you have made good improvements, and I've pointed out a few that I thought were good. Regarding the ability/PBMoveData matter, I don't have much more to add. The current data structure (that is, loading and querying the cached string data) is bad, so anything that uses it will induce a performance hit. I'm not an expert on low-level

Essentials supports 4 hidden abilities, which is why it loads four individual abilities. Essentials is built around the whole "dexdata" approach. species/abilities/forms and all that are loaded by opening the relevant data file, reading from the relevant section at the desired offset. This is an archaic data structure, but removing three string read points isn't going to make a difference. A real difference would be switching to a Hash-based data structure, like how item data is stored ($ItemData). This would actually have a noticeable impact on performance, unlike what is suggested here.