This really should have been a TPoint for consistency

merge

-gh (heaptrace) appears to be the reason for crashing in DrawCircle on my system. I wonder if it has other bad behaviour as well.

Introduced a Touch_Finger type to replace the arrays with coords, makes cleaner code

Attempt to recreate all textures if using Windows or OSX which lose textures on context recreation. Not really tested since I don't have Windows or OSX.

Added several graphics

Special case small radius gears to try and prevent repeated collisions.

Added a hook to uGame which now allows uTouch to take action outside of SDL_Finger* events Users can no walk left, right, jump up, aim, fire and are limited in zooming

teach AI about sticky mines

Fixed crash which occured when entering the teamselection menu for the second time

- Update russian translation - Perform lupdate

merge

Remove PosInStack function, as bots behave better (they search more positions) without it

aiming fixed, inverted cursor on ammo menu, added equal and isZero function to uFloat, changed the way ammo menu opens, you must now click on the hog rather than anywhere on the screen

- Updates to Tumbler gameplay mode [may still need a lil work] - New User Mission. Is this one possible?

Volume keys now work

oops

open ammo when clicking the current hog

portal: combating the space-detection issue. what needs to be tweaked next is how far away objects are spawned. it should either be a trial&error adjustment or depend on the object's moving direction and the portal's angle in order to avoid issues with box collisions. if the spawn distance to the portal is just a fixed value (as it was before this patch) or a constant factor (it is now) it can be too big for "nice" portal angles (in tight gaps with still enough space, but -> denied) and too small for bad angles (box collision esp. on big objects like barrels -> denied)

merge

Free messages queue on engine shutdown

merge

...

Now able to select a weapon

*sigh*

merge

Add square check to shotgun. This a minor optimisation that might sidestep a bug on iOS/Android. Still need to find out why the bug is happening though

Break visual gears list up into 4, to avoid iterating over entire list to draw a single layer. Also fix error in tag zoom.

Make it a lot harder to cheat with typical random crates. This also means that crates will vary even if map has the same seed (hog positions of course will be unchanged).

At mikade's request, expose screenheight/screenwidth and allow setting tag zoom level

Properly implement slot, connect signal from the object which actually sends it to the slot

Check for dX too

I'll learn to build first eventually...

uTouch, has cursor move, zoom and click or tap to open the ammo menu

oops

merge

Move HealthTag dY init into AddGear

merge

Use Frame instead of State for the health flag

Don't allow to join other protocol room using FOLLOW command (not tested)

Why so suspicious?

Allow user to drop bombs off rope, parachute, and flying saucer.

forgot scale

suggestion of mikade's - delete old mines if the collision array shows signs of filling up. This is kind of an edge case, esp now that array is up to 1024, but should prevent (easiest) way to crash by collision array overflow (endless mines/minestrikes).

bump up max collision to 1024 entries

Tiny bit of progress on download page - hooked it up to "Info" button for now.

draw health tag relative to screen if State <> 0

smaller code cleanup

For mikade's sake, use old dx/dy/frametick as default, so health crosses move the same

Use same visual gear for health tags and hearts.

Seduction animation. New visual gear type.

Shrink number of circle points to 60, reenable seduction circle (no longer crashes)

Change to "aura" due to odd crasher in DrawCircle, at least on my machine/driver. Less precise, but perhaps more attractive.

Use local scope global var instead

new SD flakes from mikade and a flash when sudden death starts

small fix for the ios project file

Some screwing around GearsNear code

Don't switch to gsConfirm state (which is pretty same as gsGame) when not in gsGame or gsChat state. Prevents crashes and other possible kinds of wierd behaviour.

Revert ParseCommandOverride change since it appears to be badly screwing up scripting. Need to find out why. This backs out 7f57d0c7816a and the recent workaround.

extend the workaround. FIXME still applies