Release 0.8

[andybalaam]

List of things to do before we can release version 0.8:

• fix On Android void flips between variants each time step #303
• speed up button on Android

Then to be able to show off our new features we need to be able to mix up the levels. I plan to do that next after 0.8. Then 0.9 can be lots of new features and levels to show them off.

[colonelfazackerley]

if #315 is found to be agreeable and there is a little more testing by someone who is not me, then i think we are ready for 0.8.

[andybalaam]

New snapshot 0.7.1.2 up at http://artificialworlds.net/rabbit-escape/snapshots/

[tttppp]

0.7.1.3 looks awesome. I just played through the first half of easy using the speed up button and it saved me loads of time.

[andybalaam]

New snapshot 0.7.1.3 up at http://artificialworlds.net/rabbit-escape/snapshots/ . This should be considered a release candidate for 0.8 I think.

Yeah, I am also loving the speed up button!

[andybalaam]

Please test 0.7.1.3 and let me know!

[colonelfazackerley]

I have played medium 1-10 on my phone. all seems good.

(Took ages to install it: turns out another app, Lux, was stopping the installer from working).

[colonelfazackerley]

I found a tiny glitch on android

• go to fast mode
• switch to another app
• switch back
• now the speed button is glowing active, but the rabbits are not fast.

its not a big problem. if you tap the button a couple of times everything is OK, but I guess @andybalaam will want it fixed.

[colonelfazackerley]

perhaps move the mute button between the pause and speed buttons. hitting speed when you wanted to hit pause is bad. hitting mute instead is less of a problem.

[tttppp]

Also, I just tried rotating the app while fast forward is set, and it gets cleared. Pause stays set when rotating, so maybe that will give a hint as to how to fix fast forward. (Note that rotating the app doesn't cause the button to be out of sync with the rabbits)

[andybalaam]

Yes on Android we must store the entire state of the ui not just the level. And yes the pause state will give us a clue. And yes it would be best to fix this before release.

[andybalaam]

Well spotted both. I should have thought of this.

[andybalaam]

I had a thought this morning. Should the fast forward button go right at the bottom? It is non-critical and you are absolutely right that accidentally hitting it could be a disaster.

[colonelfazackerley]

Players may also stab frantically at the lowest ability button and hit speed by accident.

[andybalaam]

Yes

[andybalaam]

But the explode button separates us

[andybalaam]

I am working on this.

[andybalaam]

It turns out the pause state does not give us a clue since this is stored inside World (probably wrongly). We will store speeded-up state in AndroidGameActivity in a similar way to how we store which ability is chosen.

[andybalaam]

My recent commits have fixed the problem @tttppp mentioned in #304 (comment) .

It turns out the problem @colonelfazackerley mentioned in #304 (comment) is harder to fix, so I've logged #325 and will work on it immediately after the 0.8 release.

[andybalaam]

Release 0.8 is out on GitHub and the Play store - please check it works!

[andybalaam]

The Play store here: https://play.google.com/store/apps/details?id=net.artificialworlds.rabbitescape says it's incompatible with all my devices, which is weird. Anyone else seeing anything like that? I think it just has a very wrong list of devices for me...

[colonelfazackerley]

Play page says it is compatible with my devices. Installs and runs fine from play. I verified it was v0.8.

[andybalaam]

Great, thanks.