Fix throwing things off rope, also make throwing things a bit more generic and gear density dependent (so you can throw mines further, and also throw dynamite a little).

Allow escaping from tight spots

Disable workaround, as it still makes server crash and hung clients are hidden from players anyway

Ensure crates can spawn just below the border on a bordered map.

let's see if mikade will still accept this at least

make cheating a bit easier (mikade insisted). Also, try flipping dust for a bit more variety.

oops

Hey. How's this? It makes it harder to get stuck in the vertical rope position, prevents the wall trick, and also I think makes it easier to unglue a horizontal rope?

fromdos + fix end of turn velocity

An attempt to run main rope code only every 8th tick: - A big win for inner loop which is O(n^2) and thus it takes 64 times less cpu now. - Look and feel is almost identical (well, to my non-pro view) - Yes, the speed is limited to 7 px per accounting tick which is potentially very bad to collisions - Ruin shoppa

Move rope code to separate unit

Fix formatting, reduce border sensitivity

Hedgeroid: Fixed map preview again (might be a JNA bug)

also needs exclusion here

Hedgeroid improvements: - Moved frontlib initialization to a slightly better place - Added new JNA type ByteArrayPtr to move more JNA code into the frontlib package and to improve pointer type safety

Don't leave frontend in engine waiting state when there's error occured on attempt to start engine

Hedgeroid: Some code cleanup, adding a forgotten file

Slightly faster and slightly better templates #41 and #43

License change: With the agreement of Xeli, I changed the Hedgeroid license to GPLv2+ (from GPLv2).

drawn maps have a fixed 4096x2048 area right now

Hedgeroid: Final sprint to the deadline - Changed local game setup to use the new fragments from the netroom - Pulled team editing into the main activity menu / action bar - Cleanups, renames, anything to make the code look better ;)

move this section back to the connection code, and add an exclusion for air attack. probably should play a few portal games just in case

frontlib: Improved documentation of netconn, unified naming of a callback

*sigh*

engine: Don't overwrite isTerminated if it's already true

initModule really not needed for uRandom

Fix engine crashes on game end - frontlib now waits until the engine actually disconnects - engine does not write round-end stats to stdout anymore on mobile (caused crash) - Removed HWTerminate function binding for android (not threadsafe, better send "eforcequit" over IPC for the same effect)

Burn a random number in the override. Make sure cirbuf is reset.

Merge

extra nil check for lua hog switch

Hedgeroid: Don't change the template when clicking the map.

now really avoid

Hedgeroid: Increased assetsversion (d'oh)

avoid overflow on templates

Hedgeroid: - Updated assets - reworked team management in a room - lower engine quality (for now) - added focus/disable states for spinner and button graphics

allow lua to specify template by number

frontlib: Return more filled-in team objects

merge

Cancel shotgun shot if hedgehog is moved moved (by explosion)

engine: Fixed indentation regression

koda changed the CMake flag w/o updating the wiki or INSTALL file :(

Merge

Hedgeroid: Don't update the map preview just for a theme change

oops

Hedgeroid: Fixed JNA mapping of size_t

fix the touchUI on android, ignore device dpi for now

engine: Fixed sigsegv on android caused by modifying Template.FillPoints constants

byte order

Hedgeroid: Fixed memory handling issues

Simplify code a bit

Hedgeroid: Fixed the restructuring-induced breakage

GoBack() here is not needed anymore

Merge

Avoid a bit of a memory spike on small maps

This one gets called a lot when drawing rotated sprites

Consistency

This union hasn't been needed for 5 years, and makes using other headers harder.

Forgot this state

minor changes in list of codecs

Poor visual gear value in theme now bears little resemblance to the number of gears actually spawned. But, it certainly shouldn't be related to LAND_WIDTH.