Yes I know I'm missing certain words in-between them... but every time I did one it failed. The guide didn't help me so I am quite stuck. I just need assistance on what I am meant to write on where everything is placed. Area is part of the IWRAM domain. X/Y Speed (and Spin/Slide) is in the EWRAM domain. X/Y Pos is a Combined WRAM Quick explanation on the one called "Area" Area would be one of the hidden values which will be controlling what will be shown on screen. The Areas it will be switching are at; Warp Room, Bonus, Boss Fights, Flying Sections, Normal Levels but not Polar Events (it needs a value to itself) Edit: Think I got the hang of it now, I'll post an update in a bit. After I figure out this stupid thing with the shooting cooldown :|Language: luawhile true do gui.text(0,130,"Area: " .. memory.readbyte(0x1644)) -- The only one I know what I'm doing gui.text(0,70,"Pixel X: " .. (0x010A15)) gui.text(0,82,"Pixel Y: " .. (0x010A19)) gui.text(0,94,"Speed X: " .. (0x010A74)) gui.text(0,106,"Speed Y: " .. (0x010A78)) gui.text(0,280,"Slide Time: 22/" .. (0x010DDC)) gui.text(0,292,"Spin Time 23/" .. (0x010DDC)) emu.frameadvance() end
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
Crash: N-TrancedLanguage: luawhile true do memory.writebyte(0x200345C,0) -- Boxes memory.writebyte(0x2003454,0) -- Wumpa memory.writebyte(0x200344C,0) -- Lives vba.frameadvance() end
Basically this hides each part of the hud and keeps it off screen so you don't see it. This shouldn't effect anything from the game itself. Changing the Value 0 to a 2 will show that part of the HUD. So returning to showing each part in a corner yay? And yes. It's buggy because of no verification on checking areas or stuff. Huge Adventure bug by doing this:Language: luawhile true do memory.writebyte(0x2006794,0) -- Boxes memory.writebyte(0x200678C,0) -- Wumpa memory.writebyte(0x2006784,0) -- Lives vba.frameadvance() end
N-Tranced is more effected by this cause it will crash everywhere.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
Units:
du : distance unit
f : frame
Related info:
The speed displayed by the lua script is _NOT_ the real speed (you can check it yourself by calculating the position difference between two consecutive frames when Crash starts to move). I didn't used the speed to find the fastest way to move, instead I used the position to calculate the real speed.
"start spin at frame X" means that I press the spin button when the script shows "Slide Time: 22/ X"
SSS (Slide-Slide-Spin):
start spin at frame 9 => 35744 du (over 59 frames) => 605.8 du/f
start spin at frame 10 => 36408 du (over 60 frames) => 606.8 du/f
start spin at frame 11 => 37016 du (over 61 frames) => 606.81 du/f
Slide-Spin:
start spin at frame 10 => 22096 du (over 36 frames) => 613.77 du/f
start spin at frame 11 => 22704 du (over 37 frames) => 613.62 du/f
start spin at frame 12 => 23256 du (over 38 frames) => 612.02 du/f
start spin at frame 13 => 23752 du (over 39 frames) => 609.02 du/f
start spin at frame 14 => 23752 du (over 39 frames) => 609.02 du/f
Sooooo:
best in Slide-Slide-Spin : full slide then 11 frames slide then spin => 606.81 u/f
best in Slide-Spin : Slide then start to spin at the frame 10 => 613.77 du/f
best of all : Slide-Spin 10 frame
The Slide-Slide-Spin could probably be used in some circumstances where it's needed to travel a longer distance
I modified Spikestuff's lua script (available here : User movie #21887470776514321) Change log:* Use unsigned 4b for x/y position instead of 2b * Refactorisation (well Spikestuff don't like what I did, I should probably not call this refactorisation :p)
+fsvgm777 never censoring anything.
The Slide-Slide-Spin could probably be used in some circumstances where it's needed to travel a longer distance
My other issue is Crash's Max walking speed is 512.
His slide is: 1280, 1224, 1168, 1112, 1056, 1000, 944, 888, 832, 776, 720, 664, 552+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
+fsvgm777 never censoring anything.
You need to launch this script 1 or 2 frames before the segment of frames you want to analyze, so that you can see the average speed and the speed changes. The useful thing about this approch is that you can see how fast is a set of movements regardless its amount of frames and distance travelled: you instead judge its efficiency by looking at the final average speed amount, which is actually the ratio of distance traveled and elapsed time. This same theory can probably also applied to 3D games, by adding the the other axis and calculating the resulting space travelled by applying the Pythagorean theorem. Here is a graph showing the four most common movements segments, optimized to the fullest:Language: luaplayer_x_addr = 0x010A14 frames_amount = 0 player_x = 0 player_x_old = 0 speed_average = 0 if memory.usememorydomain("EWRAM") then player_x = memory.read_u32_le(player_x_addr) console.log("Starting script at frame: " .. emu.framecount() .. " with X: " .. player_x) emu.frameadvance() while true do player_x_old = player_x player_x = memory.read_u32_le(player_x_addr) frames_amount = frames_amount + 1 speed_average = ( ( speed_average * ( frames_amount - 1 ) ) +player_x -player_x_old ) / frames_amount console.log("Frame: " .. emu.framecount() .. " X: " .. player_x .. " Speed: " .. (player_x-player_x_old) .. " Average: " .. speed_average) emu.frameadvance() end else console.log("Error: failed to set EWRAM memory domain") end
Obviously, many circumstances require customization of these moventes sets or even creating a sets of movements ad hoc. This is not a bot after all.
I've completed the first level and I think it would nearly 
I removed the Slide+Spin+Jump combo because it's just useless. The regular Slide is useful only in very rare cases, and it's actually not a combo, thus has nothing to be optimized.
Header: every object has it
allocated memory 10A04 4h
?
pointer next 10A0C 4h
pointer prev 10A10 4h
Position:
xpos 10A14 4u
ypos 10A18 4u
Animation:
state 10A38 1b
animation 10A44 1u
animation timer 10A48 1u
Physics:
x startspeed 10A5C 2s
x acceleration 10A60 2s
x maxspeed 10A64 2s
jump force 10A68 2s
gravity 10A6C 2s
max fallspeed 10A70 2s
x speed 10A74 2s
y speed 10A78 2s
jump peak flag 10A7A 2s
xpos old 10A80 4u
ypos old 10A84 4u
pointer 10AAC 4h
Last positions:
pointer 10AC4 4h
slot 10ACB 1u
lastpos's 10AC4 ~ 10B08 4u
Interaction with boxes:
pointer 10B24 4h
xpos 10B28 4u
ypos 10B2C 4u
pointer 10B48 4h
xpos 10B4C 4u
ypos 10B50 4uIt might be that back in 2015, there was no (good) GBA support in BizHawk?
The game stores the 7 last positions, useful for your script ThunderAxe.
Vertical movements graph coming soon.
One last thing: when you hit a box with the spin, you your speed will drop to 20 or so. The 
As you can see, simply tapping A every 12 frames is the fastest way of moving. Use the spin only if you have to deal with an enemy or box, since you can't really gain horizontal velocity without breaking the 12 frames combo.
Also, spins are useful for changing horizontal direction instantly at maximum initial speed of 900.
By the way, I also figured that breaking boxes does not always make you drop velocity. I will write more about it, tough it won't probably happen until I start an "100%" run.