5.1.1 Melee combat

Overview of Melee Combat on Roblox

Melee combat in Roblox focuses on close range interactions where players use tools like swords, fists, or batons to damage opponents. In Roblox terms, melee combat is usually built on top of the character model, a Tool, and a system that detects when the weapon should deal damage and to whom.

The core idea is always the same. The player equips a melee tool, performs an attack action, the game checks what the attack hit, and then applies damage to a valid target. Everything you add on top of this, such as combos, heavy attacks, or special moves, builds on that basic flow.

Melee systems are also strongly connected to animation, hit detection, and cooldowns, so you will work with those topics when you refine what you create here.

Basic Structure of a Melee Weapon

In Roblox, melee weapons are usually implemented as Tool objects that sit in StarterPack or are given to the player through scripts. Each tool has one or more parts that can deal damage and logic that decides when the weapon is dangerous.

At the most basic level, a melee tool has a handle, some visual geometry, and a script that controls attack timing and damage. The handle is what Roblox uses to attach the tool to the character’s hand and is also often the part that detects hits.

The weapon script usually lives inside the Tool and listens for the tool being activated. Tool.Activated is a simple entry point that tells you when the player tries to attack. Inside the handler for activation, you can play effects, trigger animations, and temporarily enable hit detection on the weapon’s damaging parts.

Timing and Attack Windows

Melee combat is usually not “always on.” If the weapon damaged anything it touched at all times, combat would feel unfair and awkward. Instead, melee weapons use short attack windows. Only for a small period of time after an attack begins does the weapon count as dangerous.

An attack window starts when the player activates an attack and ends when that attack’s motion is finished. Within that window, the weapon checks for collisions or overlaps with targets and applies damage one time per target for that attack.

You can create an attack window with a simple sequence. When the tool is activated, you mark the weapon as attacking, wait for the duration of the swing, then reset it. Hit detection logic reads this attacking state and only applies damage if the attack is currently active.

Careful timing of this window makes the combat feel responsive. If it is too short, attacks feel like they miss. If it is too long, players get “ghost” hits before or after their weapon visually connects.

Hit Detection Approaches for Melee

Hit detection is the process that decides what your melee attack connects with. In Roblox, there are several common approaches for melee hit detection. Each one changes how your combat feels and how accurate your attacks look.

The simplest method is to use Touched events on the weapon’s damaging part, usually the handle or blade. When the sword’s blade part touches another part, you check whether that part belongs to a character you can damage. With this approach you filter hits so you ignore your own character, your team, and anything that should not take damage.

Another common approach is to use region or ray based checks that run at specific times during the swing. In this method you do not rely on Touched. Instead, during the attack window you repeatedly cast rays or check for parts within a small region in front of the character. This can give more consistent results, especially if attacks are fast.

You can also combine these methods. For example, you can use Touched for simple, slow swings and periodic raycasts for stronger or special attacks. Each attack type can choose a different detection method while still using the same damage logic.

Controlling Damage Application

Damage is usually applied to a Roblox character by calling methods on its Humanoid. Once you have identified a part that should be hit, you travel up the model hierarchy to find its humanoid. When you find it, you apply damage according to your combat rules.

For melee combat, you rarely use fixed damage for every hit. Even in simple systems, damage is usually defined as a property of the tool, so different weapons can share the same behavior script but have different effectiveness. More advanced systems use combinations of base weapon damage, player stats, or special multipliers.

A simple way to structure this is to store a Damage value as a number under the tool or inside a configuration module. When the weapon script registers a valid hit, it reads this damage value and subtracts it from the target’s health using the humanoid API. You can add critical hits or bonus head damage later by adjusting that calculation.

To avoid multiple hits on the same target in one attack, you maintain a list of characters hit during the current attack window. Whenever you apply damage, you add the character to the list and ignore further hits on that character until the attack ends. When the attack window closes, you clear the list.

Preventing Self Hits and Friendly Fire

Melee weapons must ignore the player who uses them or combat will become frustrating and broken. To prevent self damage, your hit detection logic checks whether the part it touched is part of the same character model that owns the tool. If it is, the script immediately returns without applying any damage.

If you introduce teams or factions, you also want to block friendly fire. In Roblox, team information can come from Teams service or from custom attributes on players and characters. Your melee script reads team data for both the attacker and the target and only continues if the two are on opposing sides.

This filtering can be collected into a single helper function that receives a humanoid and returns a boolean that tells you whether the owner of the weapon is allowed to damage it. Keeping this logic together makes it easier to adjust your rules later without changing every weapon.

Attack Feel, Hit Stop, and Feedback

Melee combat feels alive when attacks are not just numbers, but also provide clear feedback. Feedback is crucial for both the attacking player and the target, especially at close range where actions happen very fast.

Visual feedback often starts with animations. When an attack begins, your script triggers an attack animation on the character’s humanoid. The timing of this animation should match your attack window so that damage happens near the moment of visual impact. You can enhance this with effects on the weapon, such as trails or small flashes.

On hit, you can briefly emphasize the impact by slightly pausing motion, playing a specific sound, or adding a small camera shake for the attacker. This tiny delay or jolt is sometimes called hit stop. It makes hits feel strong and helps players notice they actually connected.

You also need clear information for the player who was hit. Damage numbers, sound cues, and character flinches or stagger animations all help communicate that the target took damage. For melee combat, this clarity is especially important given the short distance between attacker and target.

Combos and Attack Sequences

More advanced melee systems often allow players to chain multiple attacks in a row. Instead of the same swing every time, the character cycles through a sequence of animations and hit timings when the player keeps pressing the attack input within a short time window.

A simple combo system tracks which step of the combo the player is currently on. When the attack input is pressed, if the previous attack has finished and the input is still within an allowed follow up window, you advance to the next attack in the sequence. If the player waits too long or the combo finishes, you reset back to the first attack.

Each step in the combo can have its own damage value, animation, and attack window duration. This lets you design opening light attacks and finishing heavy attacks that together feel fluid and satisfying.

To keep combos responsive, you design clear timing rules. You can define a short interval after each swing where a new input will queue the next attack. If the player presses the button inside that interval, your script plays the next animation as soon as it can and updates the active attack window accordingly.

Heavy Attacks and Charged Strikes

Many melee systems differentiate between light and heavy attacks. Light attacks are quick with short cooldowns, while heavy attacks take longer to perform but do more damage or apply special effects like knockback.

A heavy attack is usually triggered with a separate input or by holding the attack button. If you use hold behavior, your script can track how long the attack button is pressed, then use that duration as a factor that chooses between a light and heavy attack, or scales the damage inside some allowed range.

The damage scaling for charged attacks can use a simple formula. For example, you might define a minimum and maximum damage and linearly map the charge time between them. If $t$ is the charge time clamped between $0$ and some maximum $T$, with base damage $D_{min}$ and maximum damage $D_{max}$, you can define:

$$
D(t) = D_{min} + \left(\frac{t}{T}\right) \cdot (D_{max} - D_{min})
$$

You can also choose to not scale damage continuously and instead set thresholds. For example, under half of $T$ gives a standard attack, while over half gives a significantly stronger attack. This kind of step based design is easier to balance.

Blocking, Parrying, and Counters

Once you have basic input and damage working, you can expand melee combat with defensive mechanics. Blocking reduces or eliminates incoming damage at the cost of movement or stamina. Parrying is a more precise action that can stun or open up attackers if timed correctly.

To implement blocking, you track a blocking state on the defending character. When a melee hit is about to apply damage, you first check whether the target is blocking. If true, you reduce or ignore the damage according to your rules. You can also apply effects like stamina loss or a guard break if the defender blocks too much.

Parrying usually requires narrow timing. One method is to track a short parry window after the defender presses the parry button. If the incoming hit lands within this window, you treat the parry as successful and cancel or reflect the attack. This can result in the attacker being stunned or having their combo interrupted.

These interactions rely on reading both the attacker’s attack state and the defender’s defensive state. Synchronizing them correctly is crucial so that when the player believes they blocked in time, the result in game matches that expectation.

Distance, Range, and Movement in Melee

Melee combat happens at close range, so spacing and positioning matter a lot. You control the effective range of attacks by how far the weapon reaches and how you calculate hit detection. A sword with a longer blade part or a wider region for raycasts will have more reach.

You also control how much mobility a player has during attacks. Some games allow free movement while swinging, which encourages players to move during combat. Other games restrict movement during swings, which makes timing and anticipation more important.

Lunges and movement boosts tied to attacks are common. For example, a simple lunge can move the character slightly forward when a melee attack starts so the swing is more likely to connect. You can design both light steps and more dramatic dashes, but for each one you must adjust your hit detection and attack windows so that damage lines up with the character’s new position.

To keep combat fair, you usually design each weapon with a rough relationship between range, damage, and speed. Generally, longer range melee weapons are slower or weaker, and short range weapons are faster or stronger.

Balancing these values is part of the broader combat design, which connects melee combat to the rest of your game systems.