Party Minigames is a 3D online multiplayer game built around one core idea: a shared space where players can wager in-game currency across a variety of minigames. The game currently features minigolf, air hockey, poker, blackjack, and mines, with more planned for the future.
Currency earned through play can be spent on cosmetic customizations: unique golf balls, custom playing cards, poker chip designs, visual effects and particles, air hockey pucks and paddles, and more. The goal is to create a platform that feels like a virtual arcade — a place where the competitive stakes are always present, but the atmosphere stays social and fun. Certain minigames will also support local play for couch sessions.
Far from a standard minigolf experience. Players can deploy a range of power-ups mid-round to gain an advantage or sabotage opponents. These include boost panels, placeable walls, teleportation holes, icy floor patches, the ability to shrink or expand other players' balls, and bouncy platforms — among others. Each round becomes as much about strategy and timing as it is about aiming your shot.
A faithful recreation of the classic arcade staple, played in real-time over the network. The physics are tuned to feel responsive and satisfying, with plans to introduce power-ups and modifiers in the future, adding an extra layer of unpredictability to competitive matches.
A full implementation of Texas Hold'em, complete with blinds, betting rounds, side pots, and all the edge cases that come with it. Players wager in-game currency, making every hand feel consequential. The implementation faithfully follows standard poker rules while integrating seamlessly with the game's economy.
A straightforward blackjack table where multiple players can sit and play against the house. Bets are placed with in-game currency, and the rules follow the standard you'd expect from any casino — hit, stand, double down, and split.
A pure risk-versus-reward game. Players are presented with a grid containing a number of hidden bombs. Each safe cell revealed increases the payout multiplier, but hitting a bomb forfeits the entire bet. It's a test of nerve — knowing when to cash out is the entire game. Still under consideration for the final release.
Both the client and the dedicated server are built entirely in Godot using C#. The architecture follows a traditional client-server model: the server handles authentication, matchmaking, and all authoritative game logic, while the client is responsible only for rendering and sending player input.
When a player connects, the server authenticates them and places them into a queue for their selected minigame. Once the minimum player count for that game is reached, the server spins up a new lobby for the first eligible clients in the queue. Skill-based matchmaking is a possibility for the future, but is not a current priority.
For minigames that rely on physics simulation — namely minigolf and air hockey — each lobby must operate in its own isolated physics space. Without this, objects from one lobby would collide with those in another. This is achieved by creating a unique world space for each lobby using PhysicsServer3D.AreaSetParam(), ensuring complete separation between concurrent game instances.
One of the most significant challenges in developing this game is the rigorous server-side validation required for every client action. Because the server is authoritative, every RPC request from a client must be verified before it takes effect. This means checking not only that the request is well-formed and not a malicious call crafted with a packet editor, but also that the values sent correspond to what is actually possible given the current game state.
Take minigolf as an example: players can place items such as walls, teleport holes, and bounce pads within a limited range, and only in valid positions — on a surface with floor directly below and not overlapping with existing obstacles. On the client side, the placement interface makes these constraints intuitive; items appear red when hovering over an invalid location. But since a compromised client could bypass this entirely, the server independently performs the same spatial checks before accepting any placement.
case Power.Barrier: {
MiniGolfBreakableObject barrier =
Globals.Instance.GetScene("_packedBarrier", true)
.Instantiate<MiniGolfBreakableObject>();
CollisionShape3D shape = barrier.GetNode<CollisionShape3D>("Hitbox");
Transform3D t = new Transform3D(
Basis.FromEuler(new Vector3(0, rot, 0)), pos);
bool isPositionValid = !_scene.IsAnyObjectInShape(
new int[] { 6, 7, 8 }, shape, t * shape.Transform);
if (isPositionValid) {
barrier._killed += SendObjectKilled;
string n = _scene.SpawnObject(barrier, t);
usePower(playerId, index, pow, pos, rot, n);
}
} break;
Another considerable challenge lies in maintaining correct game state flow, particularly for poker. The sheer number of edge cases — players disconnecting mid-hand, side pot calculations, split decisions, all-in scenarios, and timing windows for each action — makes it remarkably easy to introduce softlocks or invalid states. Ensuring the game progresses smoothly regardless of what happens requires careful state machine design and extensive testing of every possible branch.
Because Party Minigames is an online multiplayer title, there is no standalone demo available — it requires a running server and other connected players. If you're interested in seeing the game in action, feel free to get in touch. I'm happy to host the server locally and walk you through a live session.