Hello all.
Wasn’t sure where such a thread should live, so I’ve plonked it here. The Arcade Tool has been out for a few months now and I’ve been working on a few things for it that are all terrible. Among those, I’ve more recently been working on attempting to create a Minigolf-esque game for the Arcade. This started off as an attempt to make a basic 2D physics thing but turned into minigolf when I had too much fun messing around with the ball physics.
This is still nowhere near completion but I thought I’d share it here to gather feedback on various bits and bobs so I can focus more on what’s actually needed. I’m pretty terrible at things like level design and art so I was hoping for feedback and suggestions on these areas especially.
Here’s a link to the GitHub: https://github.com/BOTDan/Minigolf
How to Setup/Play:
Video Guide: https://www.youtube.com/watch?v=HOHTO2OKS8Y
● 1. Go to this GitHub page and download the V1.1 Arcade source code.
(Side note: The old download link is down currently so I’ve put the Arcade on GitHub. Let me know if it should be taken down)
● 2. Extract the contents to a new folder.
● 3. Within the projects folder, create a new folder called minigolf.
● 4. Go to this GitHub page and download the Latest Release source code.
● 5. Copy the contents of the minigolf release folder into the minigolf folder you created.
You should have a folder structure looking like this: arcade_folder/projects/minigolf/main.lua
● 6. Return to the Arcade root folder where tool.exe is located.
● 7. In the File Explorer address bar, type cmd.
On other/older OSs, open a Command Prompt and set the directory to the Arcade folder.
● 8. In the Command window, type tool minigolf.
● 9. Play.
Video [V 0.1] :
(Quality is low because the Arcade runs at a fixed 400x300 resolution)
Current Version: V 0.1
Known Issues
- Ball will sometimes pass through solid objects.
- Ball travelling at speed will phase through objects.
- Ball will bounce oddly occasionally.
- Convex curves are relatively unsmooth.
Controls
A 
️ denotes an official control, while a 
denotes a debug control that probably shouldn’t be used.
W - Add 500 Velocity to the right.
D - Add 100 Velocity to the right.
S - Add 500 Velocity to the left.
A - Add 100 Velocity to the left.
SPACE - Freezes the ball. Cannot be unfrozen.
️ TAB - Show the scorecard.
️ CTRL - Replay level flyover cam.
️ CLICK - Everything
V 0.1
Initial Release
- 4 Holes
- Basic title screen
- Basic HUD
- Basic scorecard
- Buggy physics
The end goal is to have a full 18-hole extravaganza. Currently there’s only 4 holes, and of those, I’m only happy with Holes 1 and 4 (and slightly Hole 3 but it feels too luck-based). I’d love for some suggestions on course designs. Currently, moving barriers and fans are the only intractable items available, although this could be expanded.
You can use any/all parts of this for whatever you’d like. However, some HUD elements and all sound effects belong to PixelTail Games. The code is a complete mess, complete with missing comments (and not very useful ones) and inefficient functions. Good luck with understanding it. The console will also spam a load of debug rubbish. Ignore it.
Let me know what you think, what could be improved and what the other 14 holes (or 16, Holes 2 and 3 need better layouts) could look like.
Cheers.
