So my outdated model, the 2nd prototype, took 8165 bytes from the 27k obtainable and saved 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 normal,I’d love to have the ability to hold every state dimension to a max 500 bytes and to carry out at 4.
There will probably be 4 kinds of characters utilizing this method:
.Player, largest one in dimension at ~6kb.
.Full enemy, at ~5kb, is a clonable enemy with loads of strikes, every clone makes use of a distinct set.
.Enemy, at 4kb, are distinctive bosses.
.Short enemy, at 2 or 3kb, are easier smaller enemies, just like the hawk and the canine.

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

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

Walking is at present a monster in dimension and perf and may worsen when including the assaults that requires motion. While I don´t consider I can get its dimension 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 positive 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 verify by now?
Yeah yeah…however see, stand, stroll duck and soar are heavy processing motions that will probably be occurring more often than not throughout sport, 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 at all times like quicker and smaller, what there’s up to now is ok. At 5.5 we might have the sport going at 13, 1 level quicker than final prototype. I consider now it’s time to do a last move on these elementary states and work with the discovered values on forth.

edit: the way to 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 consequence.