So my previous model, the 2nd prototype, took 8165 bytes from the 27k obtainable and stored a efficiency from 8-20 averaging at 14.
It sported 2 completely different gamers with ~4 assaults every. This quantity is right here only for reference as that model was very streamlined for reminiscence utilization and a bit for efficiency.

So, present model sports activities 783 bytes for the system, 106 for a dummy background after which what you see on the desk for the states stand, stroll, duck, soar, pushed, push.

In basic,I’d love to have the ability to hold every state measurement to a max 500 bytes and to carry out at 4.
There might be 4 forms of characters utilizing this technique:
.Player, largest one in measurement at ~6kb.
.Full enemy, at ~5kb, is a clonable enemy with loads of strikes, every clone makes use of a special set.
.Enemy, at 4kb, are distinctive bosses.
.Short enemy, at 2 or 3kb, are less complicated smaller enemies, just like the hawk and the canines.

Back on the desk, it’s clear now we have the stand, stroll and soar states going over what I intend.

Standing is difficult as a result of it’s the state the pc is checking numerous joystick combos, that could be very time consuming . This state is predicted to get larger in measurement and heavy on efficiency as I nonetheless have so as to add checks for the assaults. A drastic answer to lock it up could be to skip drawing the standing participant if he’s already there.

Walking is presently a monster in measurement and perf and may worsen when including the assaults that requires motion. While I don´t imagine I will get its measurement a lot shorter, I´m sure I can get a 1/third pace increase by altering the primary IF layers to an ON GOTO factor. So issues are nice right here too.

Jumping is already fairly optimized however nonetheless wants the flykick added to it.

Now why all this deep craze about perf and reminiscence?? Shouldn’t they be in examine by now?
Yeah yeah…however see, stand, stroll duck and soar are heavy processing motions that might be occurring more often than not throughout recreation, so the sport pace is outlined right here. The state that takes longer, say 5.5, will set all different states to its.

While I’d all the time like sooner and smaller, what there’s to date is okay. At 5.5 we might have the sport going at 13, 1 level sooner than final prototype. I imagine now it’s time to do a remaining move on these basic states and work with the discovered values on forth.

edit: how you can know the sport pace from the chart? Choose any mixture of two states from STD to PUSH, add their perf quantity and add 2 (BASE) to the end result.