This saves around 20 frames for 3 lifts, so around a second. Going to cancel this for now to implement this. Sorry about that.
Is this normal? Gamebatte is the left, GBHawk on the right.
(Interestingly, the script I was using checks 0xD102 in System bus to display stuff, and it seems the BIOS in GBHawk vs Gamebatte is different in it's value at this point. Not sure if that affects anything)
The lag differences between the 2 are now much smaller; previously every transition would greatly lag by 17+ frames, but now the difference is more like +1 or 2 frames in Gamebatte compared to GBHawk (per transition). This makes comparing much easier for this game.
This causes a jump to miss shortly afterwards.
Attempting to just go ahead regardless by adding frames made it 4 frames slower than platformer version, and the boss then desyncs. Even then, that's assuming the last 2 stages don't mess with me (either). To assist myself in it, I resynced the platform tas to 2.3:
https://cdn.discordapp.com/attachments/280806848909541376/714704090982121532/Bishoujo_Senshi_Sailormoon_R_Japan_Platformer.bk2
And also found, and added dialogue related addresses since those keep giving me trouble.
Download sailormoon.luaSorry for the delay; something non-TAS related came up.Language: luamemory.usememorydomain("System Bus") --C020 local address = { x = 0xC020, y = 0xC023, x_speed = 0xC028, hp = 0xC05B, --mirrored at E05B, intervals of 16 npc1_x = 0xC120, --girl uses this boss_timer = 0xC157, --boss invulnerability timer boss_hp = 0xC15B, follower = 0xC24C, --flag for someone following? npc2_x = 0xC320, is_dialogue = 0xD102, --0xFF if dialogue? sprite_visible = 0xD112, --it's 30 during dialogue? story_progress = 0xD401, --Can start platformer at 6; mirrored at 0xF401 text_ended = 0xD481, --Ends dialogue at 0xFF text_progress = 0xD488, text_char = 0xD491, --current char? text_speed = 0xD492, character_id = 0xDE80, --1 = Sailor moon map_toggle = 0xDE83 } local stringformat = string.format while true do local x = memory.read_u24_le(address.x) local y = memory.read_u24_le(address.y) local hp = memory.readbyte(address.hp)/16 local x_speed = memory.read_u16_le(address.x_speed) local girl = memory.read_u32_le(address.npc1_x) local cat = memory.read_u32_le(address.npc2_x) local text_char = memory.readbyte(address.text_char) local text_progress = memory.readbyte(address.text_progress) local text_ended = memory.readbyte(address.text_ended) local boss_timer = memory.readbyte(address.boss_timer) local boss_hp = memory.readbyte(address.boss_hp)/16 local is_dialogue = memory.readbyte(address.is_dialogue) if (is_dialogue == 0xFF) then gui.text(0,75, "C:"..text_char .. " P:" .. text_progress) gui.text(0,90, text_ended) else gui.text(0,90, "Me "..stringformat('%.6f',x/65536.0).."("..stringformat('%.6f',y/65536.0)..")") gui.text(0,105, "Spd "..x_speed) gui.text(0,120, "C "..stringformat('%.6f',cat/65536.0)) gui.text(0,135, "G "..stringformat('%.6f',girl/65536.0)) gui.text(0,150, "B "..boss_hp.."("..boss_timer..")") end gui.text(0,60, "HP:" .. hp) --Need to show this in dialogue to see difficulty gui.text(0,165,emu.totalexecutedcycles()) emu.frameadvance() end
| 0, 0,...............T|
Also the 4 frame rule between transitions also affect the minigame screens. Since the number for the end stage minigame is determined at start of minigame, this means it can only be changed once every 4 frames
Edit 3: I investigated avoiding coins for the any%. Every time you have less than 50 coins you save 56 frames at the number guessing minigame since it just gives you a message "You have no coins" that can accept input sooner.
Stage 1 (One Noisy Morning) 0 coins
Stage 25 (To the Castle) 4 coins (3 from 1st screen, 1 from OoB)
Stage 26 (Storm the Castle) 45 coins
Stage 27 (Defeat the Giant Spearman) 1 coin (OoB)
Stage 28 (Through the grand hall) 19 coins, assuming 0 from blocks
Stage 29 (Kick em out!) varies, way more than 50 due to OoB
https://docs.google.com/spreadsheets/d/1XevsUFWknCozzJ7IRKbHigPpSeJnk5FJFZm4lNmFnjM/edit?usp=sharing
This means the main issue is stage 26. From the spreadsheet, I timed every screen in this stage. This was done on GBC instead of GB, since there was no lag in GBC, but the results apply as well.
Compared to ignoring coins, it seems to be fastest is skip 4 coins at beginning, then avoid as much coins as possible reset of stage. This will give 25 coins.
0 + 4 + 25 + 1 + 19 = 49 coins by 2nd last stage.
Last stage coins are unavoidable, so ignoring that.
This takes an additional 49 frames for 2-2, but saves 56 frames per end level for the next 2 stages, so it's a gain.
At this time, I gathered knowledge about several aspects of the game, including the full lists of 171 Digimon in the game with their stats, the experience curve, 166 moves, 625 encounter data instances, and 16 items. However, I eventually got stuck routing out how to effectively get past the second boss (let alone everything else), and let it slide for a few years.
glitch less
Its entertainment value has been increased substantially (in my opinion) by using the new Duel Escape Glitch to skip the tutorial duel. It chooses not to use that glitch for any future duels, as a speed/entertainment trade-off.