terrible idea for a gimmick hacking tool
-
I'm always disappointed in computers ability to let me be brute force stupid.
I have to write my own code to be stupid, which surely defeats the point -
I manually did it: The first frame you can push "A" to skip the logos is 622.
621 is too early.
-
@foone uhh I think it's relative paths, so that's probably %HOME% if you launched mGBA normally
-
@endrift hmm. I think that might have ended up as C:\Program Files\mGBA? Which my user doesn't have permissions to write to
-
@foone yeah that would be a problem
-
@endrift not a major one, just a bit of a confusing one since there was no error.
another question: am I right that you can't turn on turbo from a script? and there's no "always turbo" option, like turning off all throttles in bizhawk?
-
673 for the main menu.
yes I'm doing this manually -
@foone correct. That would require hooking into the frontend, which the scripting subsystem does not yet do
-
-
frame 766 is the earliest you can press A for New GAme
-
@endrift ahh, missed that! thanks!
-
@endrift and I just crashed it. unfortunately I have no debugger or anything installed here so it just vanished... is there a log file I could look at?
-
I was accidentally running multiple copies of the same script all trying to push keys at specific times.
this created some HILARIOUS non-deterministic behavior! -
@endrift is there a way for my script to ensure only one copy of it is running? if I reload it (by using recent scripts), I get two copies running. I have to reset/reload instead. can my script do that itself somehow? unload any prior copy?
-
882 is the earliest you can select slot 1.
it's those fade-ins, fade-outs. those things take forever.
-
Here's how I documented it.
My script runs the game to frame 2000, after pushing the A button at 4 different times. Then screenshot. I can tell from the thumbnail if it made it to the dialogue or not! so I just manually bisect the numbers until I get minimums.
-
so I did all this, and that's good, but I've not gotten much sleep and this took a couple hours.
so... I've completely forgotten WHY I needed to do this.
-
I suppose just to streamline the testing of patches to modify parts of the game. It certainly does that.
-
but I can't remember if I had anything more specific in mind before I got detoured into switching emulators, kinda*.
* I started with TASing on BizHawk, and then switched to scripting mGBA. This was for Reasons, but it also didn't really happen? I only changed emulator frontends, not emulators. I was using the mGBA-core in BizHawk in the first place, so I was always using mGBA. I'm just now using it directly (in its own frontend) rather than as a module in a different frontend.
-
I may be a fool: I've been trying to figure out how to hack sprites off a scene that HAS A MOVING CAMERA
I bet I can just hack the camera position and make it scroll off to -32767, -32767 or something
