Sound effects would breathe some life into the game as it feels hollow without it. Since these are retro style games, even simple sounds would suffice as it'd give feedback to what is happening on screen e.g. a beep whenever you clear lines in Tetris.

Name

Tempest

Description

Tempest Wikipedia article

The player is looking down a 3D "pipe" (for lack of a better word) of various shapes and sizes. They cling to the edge of the pipe and traverse around the circumference, as monsters climb from the end to the front of this "pipe". From any position, the player can shoot at monsters in front of them. When monsters get to the end of the pipe, they walk around the circumference for a brief period (and hence the player risks running into them) for a brief period.

Links to screenshots / videos / descriptions

Gameplay video - Youtube

Multiplayer Handicap

• More creatures spawn at the start of the tunnel each time other players score.

I'm blasting away that last asteroid and blam, I'm dead, but in that last few milliseconds I've still been pressing the area of screen where the Fire! button was. Now I'm playing Tetris...

Could we have something that prevents thus, as I'm in an Asteroids blasting mood 🙂

IMHO just putting a "Stay Here" ("Insert coin"?) / "leave" option in a different area of the screen would be good.

Thanks for this great game(s) 🙂

Describe the bug As I described in the title the game crash when I reach a score 250.000 - 300.000. I always had that bug from a very previous release. It happened in both effects retro and non retro.

To Reproduce Just playing until it crashes.

Expected behavior Thank you so much for your effort to developing!

Smartphone (please complete the following information):

• Device: Motorola one hyper
• Android Version: 11
• Version RPFS31.Q1-21-20-10

First of all: Thanks so much for the effort you put into the games! I love the app and enjoy it very much!

I think this is just a small bug, but somehow annoying, when listening to a podcast or music at the same time.

Describe the bug There is some sound effect playing at the end of each use of the thrust although sound effects are muted.

To Reproduce Steps to reproduce the behavior:

1. Mute sound effects
2. Play Asteroids and use the thrust

Expected behavior No sound

Make it so that at the start it's slower and gradually gets faster, as, well as space out the bricks slightly more to allow to cool combos in the bricks behind, while leaving the other bricks in front intact.

Is your feature request related to a problem? Please describe. After playing a few games of Breakout I came to the quick realization that unlike the other games that have on-screen buttons, this game was made with the intention to have the player drag their finger across the screen to guide the paddle. At first I was ok playing like this however some things became very apparent.

1. The paddle had a set speed.
2. The paddle's set speed was way to slow to follow my finger.

This is frustrating as when the ball is on the other side of the screen i would instinctively flick over to it but the paddle is unable to keep up making me lose lives.

Describe the solution you'd like I think that increasing the speed so that it can accurately track the player's finger even at high speeds.

Describe alternatives you've considered Currently the way I play breakout is by having my thumbs at the edges of the screen and tapping to move the paddle sort of like having pseudo buttons. I think it would be cool to have this control scheme inplemented into the game as an extra control layout in the options menu.

Name

Breakout

Description

Breakout was released in 1976 by Atari.

There are numerous variations throughout history. Some of the ones I played growing up (in chronological order) include:

• Aquanoid
• Arkanoid
• Block Breaker
• DX Ball
• Ricochet

Alas, I never actually played the original that I am proposing here!!!

Of course, there are many more in between, each with their own slant. The proposal here is to go for the original one, because it will fit in best with the simplicity of the other games here. In the future, perhaps it can stray towards something more complex or modern.

Controls:

• Use the touch screen controls to drag the paddle left or right. If this proves to be too easy, then use soft buttons on the screen to move left or right when holding the buttons.

Links to screenshots / videos / descriptions

• Wikipedia article
• YouTube playthrough

Multiplayer Handicap

A few suggestions:

• Add additional blocks to the screen in random locations. If the screen is already full of blocks, just keep adding them below the normal starting row of blocks.
• Speed up the ball (but does it speed up forever until the speed of light?)
• Reduce the size of the paddle (but does it shrink forever until it is gone?)

Name

Space Invaders

Description

In some ways, this is the quintessential retro game.

Here is some details of the mechanics to help in implementing the game.

• Multiple rows of aliens move left to right.
• When they hit the edge of the screen, they change direction and drop down one row.
• If you remove an entire column from the edge of the alien grid, that means they need to move further prior to hitting the edge.
• As the number of aliens reduces, the speed of the entire grid increases.
• You can only shoot one bullet at a time. Once shot, the bullet needs to either hit an alien or the top of the screen prior to being able to shoot again.
• There are shields protecting the player. As they are hit, they disintegrate reducing the production.
• You can also shoot through the shields if you want to make space to shoot aliens while maintaining some amount of cover.
• Periodically, a faster moving spaceship moves along the top of the screen above all the aliens.
• Once all the aliens are removed from the screen, a new grid appears again, signifying the next level.

Links to screenshots / videos / descriptions

• Online emulator of 1985 Sega version - Internet Archive
• GamePlay video of 1978 arcade version - Youtube

Multiplayer Handicap

There are various options here. Things to consider:

• Add more aliens to the screen (perhaps the most obvious), though use some heuristics to ensure that they appear near the top of the list of current aliens, otherwise they may spawn in a nigh-on-impossible-to-defend-low place that then instantly hits the ground - especially if your current remaining aliens are moving very fast.
• Increase the speed of the current aliens
• Remove the shields from the screen

Of these I think it would be best to just go with adding more aliens.

I added nb_NO and it locked the translation component I added. If you add "kingu" in https://hosted.weblate.org/access/retrowars/#users I can have a look. :)

Describe the bug Upon opening v0.6.0 of the app built from F-Droid, it crashes immediately with the following logcat:

07-07 13:18:27.438 29137 29137 E AndroidRuntime: FATAL EXCEPTION: main
07-07 13:18:27.438 29137 29137 E AndroidRuntime: Process: com.serwylo.retrowars, PID: 29137
07-07 13:18:27.438 29137 29137 E AndroidRuntime: java.lang.ExceptionInInitializerError
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at java.lang.Class.newInstance(Native Method)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.AppComponentFactory.instantiateActivity(AppComponentFactory.java:95)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.Instrumentation.newActivity(Instrumentation.java:1264)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3797)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4077)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:91)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:149)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:103)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2458)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:110)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:219)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:8387)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: Caused by: com.badlogic.gdx.utils.GdxRuntimeException: Couldn't load shared library 'gdx' for target: Linux, 32-bit
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at com.badlogic.gdx.utils.SharedLibraryLoader.load(Unknown Source:82)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at com.badlogic.gdx.utils.GdxNativesLoader.load(Unknown Source:25)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at com.badlogic.gdx.backends.android.AndroidApplication.<clinit>(Unknown Source:0)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	... 15 more
07-07 13:18:27.438 29137 29137 E AndroidRuntime: Caused by: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.serwylo.retrowars--2YQ84TtOIOhFUYmf_3Vpg==/base.apk"],nativeLibraryDirectories=[/data/app/com.serwylo.retrowars--2YQ84TtOIOhFUYmf_3Vpg==/lib/arm64, /system/lib64, /hw_product/lib64, /system/product/lib64, /prets/lib64]]] couldn't find "libgdx.so"
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at java.lang.Runtime.loadLibrary0(Runtime.java:1067)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at java.lang.System.loadLibrary(System.java:1668)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	at com.badlogic.gdx.utils.SharedLibraryLoader.load(Unknown Source:24)
07-07 13:18:27.438 29137 29137 E AndroidRuntime: 	... 17 more

To Reproduce Steps to reproduce the behavior:

1. Download v0.6.0 from F-Droid
2. Launch the app
3. It will not open

Expected behavior App launces as per normal

Screenshots N/A

Smartphone (please complete the following information):

• Device: Huawei P30 Pro (but likely any device)
• Android Version: 10
• Version v0.6.0

Is your feature request related to a problem? Please describe.

Touch screen controls can be hard to play with due to lack of physical feedback when pressing them. Sometimes you don't know whether you actually pressed the buttons or not.

Describe the solution you'd like Small vibration when pressing any onscreen buttons. Would need to experiment to see how much vibration, how to handle long holds vs repeated presses, and how to make it not clash with the multiplayer attack vibrations.

Should keep an option to turn this on (or default to on and option to turn off - if it turns out to work well).

Additional context This was hinted at via feedback from a kind Google Play reviewer.

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Describe the bug There's a few seconds after your ship is destroyed and before it respawns where you can be hit a second time. The ship will turn invisible but the collision is still there and you can't move.

To Reproduce Steps to reproduce the behavior:

1. Start a game of Space invaders
2. Destroy as many aliens until ther are only a few columns of them left
3. Wait unti you get hit (you should have 2 lives left now)
4. Wait for a second projectile to be shot in the seme location before you respawn.
5. Your lives have dropped twice

Expected behavior You shouldn't be vulnerable to projectiles while your ship is not on screen

Screenshots I'll see if I can manage to record a video of it

Smartphone (please complete the following information):

• Device: OnePlus Nord CE 5G
• Android Version: 11
• Version of the game: 0.31.6

Describe the bug Issue occurs every now and then, when playing Asteroids. When tapping the "move forward" button, the propulsion sound plays. When tapping the button very often within a short time (e.g. 5 times per second), the sound will continue to play, even if you exit Asteroids and go back to the main screen of the app. Only thing that helps to stop the propulsion sound is closing the app in task manager.

To Reproduce Steps to reproduce the behavior:

1. Go to 'Asteriods'
2. Play for a while and
3. Click on 'move forward' button several times in a high frequency (e.g. 5 times per second)
4. The issue is not always reproducible.
5. Hear the error: propulsion sound never stops playing, until you exit the app.

Expected behavior Propulsion sound only plays when the respective button is pressed. Pressing the button in high frequency should not cause the described bug.

Screenshots n/a

Smartphone (please complete the following information):

• Device: OnePlus 8T
• Android Version: 11
• App Version: 0.31.3