Open NewAlexGamer opened 2 years ago
Should probably send the macro file for Absolute to look at.
json nor mhr are supported, any idea? i mean i can send the json as txt if you want xD (nevermind it doesn't let me send the txt either)
json nor mhr are supported, any idea? i mean i can send the json as txt if you want xD (nevermind it doesn't let me send the txt either)
I just recommend you get echo bot. It never breaks for me and even after Replay System was released I still use echo. In my 5 months of botting levels it only broke twice.
it's not about breaking, i'm fine with it. i have fun finding bugs and how could i help improving this if i'm not using it in the first place
wait now that i think of it, while i was botting the evasium wave with frame stepper, it teleported me for some reason to those triples when i respawned. the checkpoints were still there but they were just sprites, didn't have any function attached to them, so i had to go back to evasium i guess this has turned in another frame stepper bug showcase indisguise edit: i figured out that i can simply zip the macro, i'm stupid yes aaaaaaaa.zip
I'm having a similar issue, here's Cycles.
i was botting a very totally humanely possible path for bloodbath. while i was botting nothing seemed to have gone wrong, although i wasn't constantly checking the frame count to see if everything was alright. once i replayed to see if it properly worked and to admire the absolute waste of time i put into doing this stuff, i got to michigun's part and noticed it wasn't jumping at all therefore i exported to json to manually edit in the jump, but instead found this:
as you can see about 1000 frames are completely missing and the frame replay got stuck at is one of those. while the jump at about frame 5500 was working, it wasn't even showing up in the json
ingame this was happening:
https://user-images.githubusercontent.com/86263500/184688866-e248c12e-8cee-4b7c-9a0b-da936402f061.mp4
replay was stuck after frame "5567" and started working again after you enter the evasium's wave at 36% the thing is that it didn't skip to i don't know, frame 6300 or something, instead continued from frame 5567 like nothing happened incredibly_broken_bugs_found++;