User Files for Dungeons & Dragons: Eye of the Beholder

Nonfunctional. Do not run.

Been looking over my older stuff to find this script. It is an attempt at botting (or more accurately, simulating) the first battle, so that I can see this fight perfected, but it is decidedly incomplete, and it is not structured to treat the fodder with ambiguous stats, so it needs a redesign anyway.

Note that the script shouldn't be running emulator functions. It's just a scripted simulator, not a savestate bot.

Fourth exhibit.

This is the data extraction script I've been using for that... One game... For the GBA. Actually, it's less of a script and more of a set of functions. I forget what I was using it for last, but I've adjusted the code every time I needed to get at another piece of information.

The code could be better organized, but anyone messing with this had better know a few things about lua before trying this script. I have put no provisions for others to use this, as it was strictly for me to use, and me alone. Oh, and anyone messing with this script should also have a really good idea about data structures, and a helping of some rather interesting intuition, since it was certainly non-trivial to work out what every one of those internal bytes in the game meant.

Not for the casual viewer. The more technical you are, the better. If you have no confidence in computer stuff, well, tough. You're looking at the wrong script. It's bleeding edge experimental stuff that can only be operated by someone willing to put significant time into it.

For use with VBA, though.

For BizHawk. Geez, those forms work slow. I recommend pausing the script when you want to use turbo mode.

Currently predicts d4, d6, d8, d10, d12, and d20 rolls. It gives some pride that I can't detect errors with its predictions, but on the other hand, this could also mean my error detection might need work. Regardless, I think I know all the dice rolls in the future!

It spawns a single window with a list of numbers. Each column reports dice of different sides, with the top numbers being the immediate next result. Anyone here fluent in object properties and can tell me how to right-justify the labels?

BizHawk 1.9.1

I don't know where my TASing mood is going, but currently it seems it says I'm not done with this game yet, what with all the analyzing I've done elsewhere.

It is critical that we take the time to kill off two members, as the game insists on having you run with a four-person party, and this divides up the experience necessary for extremely useful spells. Notably, since I'm just checking a route, I did not manipulate luck as much as I should early on. The route seems to work.