Sun, 08 Dec 2013 13:49:11 -0500 Add missing gstCollision bug #725
nemo [Sun, 08 Dec 2013 13:49:11 -0500] rev 9767
Add missing gstCollision bug #725
Sun, 08 Dec 2013 17:58:45 +0100 fix Issue #724: Bee sound never stops (underwater when timer is 0)
sheepluva [Sun, 08 Dec 2013 17:58:45 +0100] rev 9766
fix issue #724: Bee sound never stops (underwater when timer is 0) also: instead of flowers add bubbles while underwater
Sun, 08 Dec 2013 12:19:30 +0100 string/typo fixes
sheepluva [Sun, 08 Dec 2013 12:19:30 +0100] rev 9765
string/typo fixes
Sat, 07 Dec 2013 22:09:55 -0500 revert r938d1c08d0d1 in favour of putting it in the chat log. I think this addresses main concern about missing text. There've been complaints in past too about conversation in bubbles not being visible in history. If the objection is that r938d1c08d0d1 offers a more ├Žsthetic solution, I think it should augment this, be flagged, and fix the visual issues first.
nemo [Sat, 07 Dec 2013 22:09:55 -0500] rev 9764
revert r938d1c08d0d1 in favour of putting it in the chat log. I think this addresses main concern about missing text. There've been complaints in past too about conversation in bubbles not being visible in history. If the objection is that r938d1c08d0d1 offers a more ├Žsthetic solution, I think it should augment this, be flagged, and fix the visual issues first.
Sat, 07 Dec 2013 21:41:34 -0500 use a variable that allows negative values instead.
nemo [Sat, 07 Dec 2013 21:41:34 -0500] rev 9763
use a variable that allows negative values instead.
Sun, 08 Dec 2013 02:43:06 +0100 disallow speech bubbles to go offscreen
sheepluva [Sun, 08 Dec 2013 02:43:06 +0100] rev 9762
disallow speech bubbles to go offscreen no tint or tail-directio adjustments for indicating it's offscreen yet though
Sun, 08 Dec 2013 02:36:14 +0100 fix speechbubbles assigning negative values to a Longword value, overflowing it
sheepluva [Sun, 08 Dec 2013 02:36:14 +0100] rev 9761
fix speechbubbles assigning negative values to a Longword value, overflowing it
Fri, 06 Dec 2013 23:53:35 +0100 It seems that at the current state it is necessary to protect sending stats/ending game from multiple execution,
sheepluva [Fri, 06 Dec 2013 23:53:35 +0100] rev 9760
It seems that at the current state it is necessary to protect sending stats/ending game from multiple execution, as that can happen if you e.g. fail a mission more than once in the same tick (e.g. destroying two essential crates at the same time) Otherwise you can get a blank / stuck frontend (e.g. when using deagle to shoot the two last crates at the same time)! the best approach might be to never call the function that sends stats and ends game from any event handler directly, but instead have a flag 'isFailed' that is set to true when any of the possible fails happen and to check that flag every tick to send stats and end game if true
Fri, 06 Dec 2013 22:48:30 +0100 * turned out the no-flight zone is also a no-climb-and-progress zone
sheepluva [Fri, 06 Dec 2013 22:48:30 +0100] rev 9759
* turned out the no-flight zone is also a no-climb-and-progress zone * also changed it to not completely nullify velocity (otherwise cliffjumpers can get stuck in midair), just make sure dy is not negative
Fri, 06 Dec 2013 20:38:48 +0100 some more campaign string tweaks
sheepluva [Fri, 06 Dec 2013 20:38:48 +0100] rev 9758
some more campaign string tweaks
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip