Gameplay programming and technical game design

Bencci: Combat and progression in a four-Duo arena

Four Duos fight in two simultaneous 2v2 battles and change their builds between Cycles. I design and program Bencci on my own, from Deadeye’s ricocheting shots to the rules that carry each build into the next fight.

Practice Championship trailer. Player 001 spends points in Preparation, fights a 2v2, chooses an Evolution and fights again. Solar wins, and the player checks the standings and Profile history before returning to Home.

Bencci uses provisional AI-generated art for development and testing.

Role
Solo Programmer and Designer
Context
  • Personal project
  • in development
Period
Ongoing · 16 November 2026 snapshot
Status
  • Playable development prototype
  • unreleased
  • Unreal Engine 5.8
  • C++
  • Gameplay Ability System
  • Enhanced Input
  • Blueprints

How a match plays

I built the match around a 2v2 so you can read the opponents in front of you and coordinate with one partner. Each battle still counts toward a four-Duo competition.

  1. Lobby

    Choose your Contender and join a Duo.

  2. Preparation

    Spend earned points, rank abilities and choose an Evolution when offered.

  3. Combat

    Face your assigned opponents. The two 2v2 battles can finish independently.

  4. Results

    See the battle result. Strikes can eliminate a Duo.

  5. Restoration

    Return with your build if you’re still in contention, then prepare for the next Cycle.

Final Results. At the end, Duos see their final placement. If the last two Duos draw and both reach five Strikes in that result, the four finalists return for a Championship decider.

Deadeye’s combat kit

Deadeye is the first playable Contender I built. A ricochet can set up a Mark, give your partner a shot or open a route for a teleport.

Q · Ricochet and Marks

Q pierces targets, bounces off geometry and leaves a Mark. I wanted players to route shots through both opponents. If a wall bounce alone could keep damaging the same enemy, there would be much less reason to look for a second target.

By default, each Q projectile remembers its last valid target. Hit another valid target first and the projectile can damage the original target again. One Evolution allows a return hit after the projectile fully exits and re-enters the target.

I store Marks with the player who applied them, so that player can refresh their setup and either member of the Duo can use it for Carom or a marked teleport.

Consecutive contactA → A

The second contact deals no damage.

Another valid target in betweenA → B → A

A can take damage again.

A and B are different opponents. The sequence applies to a single projectile with its default rules.
Earlier Q ricochet and Mark test, not the integrated Deadeye milestone. This clip does not establish the complete A → B → A sequence.

Manual Basic Attack and Attack Move

A manual Basic Attack fires where you aim the cursor. Attack Move sends Deadeye toward a point and can pick up an eligible enemy he sees along the way. I show command feedback locally so you can decide whether to commit or change course. Both use the same attack timing. The server checks whether the attack is legal and resolves hits and damage.

W · Carom

Bank a shot off a surface to arm it, or take a direct shot at an enemy carrying a matching Duo Mark. The server tracks valid reflections and checks the Mark before accepting the single hit.

E · Dash and marked teleport

Dash to reposition, or commit to a teleport toward a marked opponent. The server checks the target, range and landing position. The teleport leaves the Mark available for another follow-up.

Prime · Killbox

Throw a device that creates a field where it lands. Players can cross it freely, but compatible shots bounce back in when they try to leave. A Duo can set up new Q and Carom angles inside the same space.

I put the release timing on the server and let the throw animation follow it. A released device can finish its flight if the caster falls. The battle owns its cleanup.

Build choices between fights

During Preparation, you can spend earned stat points, rank up abilities and choose an Evolution when one is offered. That lets you adjust your build to the Duos still in the match. In the showcase, Player 001 upgrades Q from rank 1 to rank 2.

One Evolution raises Deadeye’s Mark capacity from one target to two, giving your Duo a choice of follow-up targets. I keep stats, ranks and Evolutions on Unreal’s PlayerState, so your build carries into the next Cycle when the server restores your Avatar.

What each player can see and do

While you control a Contender, your Duo’s vision determines which opponents you can see. Once your battle settles, you can watch through permitted spectator views. The server authorizes each view and filters what it sends to each client to keep hidden opponents outside that view. I’m still refining how those transitions look on screen.

I implemented combat in C++ with Unreal’s Gameplay Ability System and used Blueprint assets for tuning and presentation. The server checks which battle a command belongs to and resolves hits, damage and confirmed movement. Animation and effects show those outcomes.

From lobby to match history

In this local development match, Player 001 invited Player 002 to a private Practice Championship. Six bots filled the other seats across four Duos. Once both players were Ready, the development coordinator admitted them to shared Preparation. The Duos then split into paired 2v2 battles, with a result recorded for each battle before the next Cycle.

Player 001 left during Preparation and returned through Reconnect to game. The match reservation let the server recover their original seat. Their build belongs to the match participant, so they could resume with the same choices after reconnecting.

I retain the match result in the local development profile, where players can revisit the standings and combat stats. Solar finished first in this match. Player 001’s History entry shows Victory with 13 kills, 2 deaths and 5 assists, the same numbers as their row in the final standings.

Developer showcase

Two players ready up with six bots. Player 001 spends points, ranks up Piercing Strike, fights and chooses an Evolution. After reconnecting, they win with Solar and revisit the result in Profile history.

My contribution

I own the gameplay design, programming and integration. I used Epic mannequin and Adobe Mixamo animations, prepared prototype assets in Blender and integrated the audio and effects.

I built the main menu, friends and party flows, and the lobby where players choose a Contender. Players can remap controls through Enhanced Input, keep those bindings after restart, and adjust graphics, text size, contrast and privacy settings.

What you can play today

Bencci is playable in local development builds and has run with connected multiplayer clients. It remains an active, unreleased prototype. The repository is private.

What I’m building toward

I want Evolution choices to change how a Contender plays during a match. Dynamic and destructible terrain is a future goal, with destructible terrain deferred. I’m continuing work on counterplay, responsiveness and multiplayer presentation.