Welp. We have a bit of a problem here. Reverting the move of nextturn. But this causes a desync in scripting unless we can find a better fix.
Implemented game launching API for the frontlib.
It is still buggy though, and not all game settings can be conveniently created/modified yet.
Don't make unnecessary calls to TestWhip, TestFirePunch, TestBaseballBat and TestHammer functions as they have no need to take Targ parameter into account and thus may only be called once per position
Workaround for
bug #144. This workaround had occurred to me a while ago, but wasn't sure if placing them unfairly was better than not placing them at all. Argument for not placing at all is people should probably abort the game when they notice it. Argument for placing unfairly is people can still abort, and if we really wanted them to abort, we should probably just have halted launch if all hogs failed to spawn. This way at least play can continue.
Frontlib: Work on the callback mechanisms for IPC
Work commit; It compiles and runs but will need a major overhaul tomorrow.
After experimenting with a long running average at maxed out FPS and a variety of map sizes, 128 seems to actually be a good size to use if only drawing bits of world with stuff in it. 64 actually did even better in some situations, but significantly worse in others (lots of land, zoomed out).
frontlib refactoring
socket.h now completely wraps all the lowlevel neworking, so it would be easy
to switch away from SDL_net if needed. Also reduced global state by making an
IPC connection an object-like thing.
Only create textures for non-empty LandPixel chunks. This should save a fair amount of memory, especially on smaller maps, and eliminate a number of draws
warp sound when AI survival hog respawns. attempt at a bit of a crate spawn animation (moar sparkles and a quick fadein)
Android: added a callback to java to determine dpi/dip how much we should scale the ui