OBT v1.1.1 - bug fixes, shield hp upgrade

Hello everyone!

This update brings two major bug fixes:

<dt style=>The pickup system to avoid duplicate weapon choices now is working</dt>

- Sorry for this bug, it was really a stupid mistake I made when refactoring the code and then I forgot to check it...

The quads are no longer interfere with the boss system

- They will no longer prevent that a boss appear by consuming their slots.

- I forgot to detail how the system works on the previous devlog. The boss system works as follows:

+ At the end of certain waves a specific enemy will appear;

+ It's a way to introduce the enemy before it starts to span in the middle of the wave;

+ The first is the triangle, at the end of wave 3;

+ The second is the flock of 2 quads, at the end of wave 7;

+ The third is the flock of 3 quads, at the end of wave 11;

+ The fourth is the flock of 4 quads, at the end of wave 15;

+ The pentagon starts to appear at the end of the wave 20 and will keep appearing at the end of all waves after that;

Second, now the enemy counter (the fading hexagons around the circle) will indicate when an enemy that uses multiple slots will appear. Notice on the GIF bellow how before the quad flock is spammed four enemy counters fade. The same will happens with smaller flocks and with the petagon (starting with this update teh pentagon will use 5 counters).

Third - this is a feature I forgot to include on the previous devlog - now on PC you can use any key you want on the keyboard - excluding the Function keys and the numpad (DragonRuby don't supports the numpad by default. Lucky, it's an open-source(ish - it has close source code for exporting to some platforms) engine, so I will try to enable it when I have time (and willingness). It shouldn't be hard to do it).

Finally, the shields.

• Any shield you manage to keep until the end of the wave now will be restored to full health.
• If you have 3 shields and kill a flock of 3 or 4 quads, your shields max HP will be increased by 1 (the limit is 5) and will be restored.

And, yeah, that's it for this update. Hope you like it.

PS.: I noticed that for some reason the HTML5 version performance is pretty bad even when disabling some effects by default in order to reduce the number of objects rendered... I will try to fix it, but for now I will just disable it. Sorry for that... I've been focusing on the android version and neglected the HTML5 build.