top of page

LCBeatBoxerMod

[Beta] "The Beat... The Boxer... An enemy mod centered around audio and combat."

A mod with the goal to teach me complete ownership over a feature: from design, to programming, to enemy AI, to sound design, to modelling, rigging, UV mapping, texturing, and animating.

​

On top of that, I wanted to stay true to Lethal Company's aesthetics and make an enemy that did not feel as "cheap sci-fi".

LCBeatBoxerMod v0.3.1 Demo - Highlight Reel GIF.gif
LCBeatBoxerMod: adds two enemies that I designed, programmed, modelled, and animated all by myself
Video demo with audio

Creation

To create an enemy, I would need to do three things:

1. Basic Unity Research

To learn the Unity components, I read up on the online Scripting API, to read the basics of the NavMeshAgent Classes’ different properties and methods. But I learned the most during…

My first tests with enemy code in Lethal Company, seeing how to make NavMeshAgents move toward or away from specified points

2. Enemy Behaviour Coding

I then went into Lethal Company and created an enemy prefab using the game's scripts. 

 

I made my test-enemy roam the map until it noticed a player and dropped a colored item. If this item’s color is red, the enemy would run as far away as possible, if green, as close as possible. The player could swap these colors, but as long as the player holds the item, the enemy would run to the player.
This already taught me the basics of NavMeshAgent parameters and the game's codebase.

3. Visual Design

For the model, I decided to stick with a simple idea of gorillas, and sketched some ideas.

​

While creating the model in Blender, I experimented with a handful of attempts, to figure out which prototype got close to the intended vision. I then set up an Armature with bones and weight painted it.

​

By studying Lethal Company again, I learned about multiple useful components: BoneRenderers, Rigs, RigBuilder, and Two Bone IK Constraints. These let me automatically bend bones to visual points, which massively sped up the animating.

BeatBoxer initialSketches.png
Sketching to get an idea of what the enemy model could look like
BeatBoxerModelling.png
Using what I learned from LCGoldScrapMod to rig and weight paint a more complex enemy model
2025-02-05 two bone hint GIF.gif
Learning Unity's TwoBoneIKConstraints to make animating much easier than I'd expected

And I managed to set up everything from the code to the model to the inverse kinematics very well for my first attempt, so I could move on to making the actual content next.

The Beat

The Beat was the first implemented enemy. Its intent was to trick players.

​

In Lethal Company, footstep sounds are how players are informed about enemy presence, so I flipped this idea on its head, and wanted it to try to ambush players.

Video demo for the enemy "The Beat"
LCBeatBoxerMod BeatEnemy one-pager.png

Gameplay Loop:

  • Its footsteps can be heard from far away, establishing a connection between enemy presence and this sound.

  • When spotted, it will roar and give chase for a bit to establish this enemy as a threat.

  • Afterwards, it will run away and go quiet, to give players uncertainty as to where it is now.

  • It places a Monkey Toy somewhere, and hides itself somewhere else closeby.

  • The Monkey Toy then plays identical footstep sounds, making players believe it is now in this location, while actually hiding elsewhere.

  • If players avoid the sound, they might run into the enemy. Or, if they try to steal the toy, the enemy will be enraged and chase after them.

One-Pager for the enemy, where I learned the structure of two keywords, three pillars, two intents

Programming An Ambush:

The enemy's ambush was a challenge, since Lethal Company's randomly generated levels can't guarantee the enemy to have enough space to hide. So, I simplified the idea:

  • The enemy needs one point to hide itself and one to hide the Monkey Toy.

  • These points should be far away from the player, to make it unclear where the enemy has gone. But they should be close to each other so that if the toy is around one corner, the enemy is around the other.

  • With this combined, I go through all navigation nodes, and check if a node is far enough away, and register it if it is.

  • At the next node, I check if it's close to and around a corner from the registered node, and register it as the second point if it is.

  • Repeats until it found the farthest nodes, and uses these to hide itself and the toy.

BeatBoxerBeatAmbush.png
Note of how to simplify and implement something as complex as "an ambush"
BeatBoxerMonkeyToy.png
BeatBoxerMonkeyToyPrefab.png

Audiovisual Theming:

Testing showed that the idea worked well, so I moved to aesthetics. I wanted to unsettle players without making it gory, while adding potential for comedy to emerge.

  • For footstep sounds, I picked the sound of a timpani as a low, unsettling sound, without being invasive.

  • I wanted the Monkey Toy to be unsettling as well. Now, I could combine the infamous cymbal monkey toys with the timpani theme. So, I modeled and animated it, making sure to mimic the enemy's sounds for the ambush to work.

  • I felt I was now getting close to some sort of comedy, and a theme of these enemies being performance animals was slowly starting to take shape. So, for the attack-sound effect I implemented a drumroll building up to a big cymbal hit, followed up by a cheering audience if the attack killed the player. This very nicely combined the enemy's design with the horror-comedy of the game. So, I think I managed to follow this enemy’s intent very well with its aesthetics.

Intended design of The Beat's Monkey Toy
Initial model for the Monkey Toy, emphasizing its eeriness
Video demo of an ambush of The Beat, including all its sounds
Video demo of the Monkey Toy's unsettling eyes
BeatBoxer doc concept 1.png
Documentation laying out how the enemy was first intended to be one enemy, but would fit better if it were split up into two enemies

Documenting Its Concept:
At the start of development, I created a
document for the enemy, to understand the thought process that lead to the idea and follow any leads that could make this idea interesting.

 

To bring this enemy to pre-production, I created the One-Pager shown above. I chose two main words to capture the enemy’s essence, summarized three pillars to achieve this, and then went into more detail about the intended experience. This greatly helped develop the design vision, thanks to the conciseness of this document.


And finally, to document specific details about why or how to implement this, I created a Q&A-style document where I go over the specific pillars and design decisions and explain their reasoning. This helped bridge the gap between detail and conciseness, allowing for more detail in case I ever needed to review or share certain details.

Scope Changes:
The Beat was
intended to be much more involved than it is now. The intent was to have the ambush be the first half of its loop, and then perform a second half where it would try to fight.

However, this took too long for Lethal Company. So, I split what was going to be The BeatBoxer into two enemies: The Beat and The Boxer. Now, I could focus The Beat on just its own functionality. 

BeatBoxerReworkDocument.png
Problems from initial playtests, with proposed solutions
BeatBoxerNudgeToMidpoint.png
Code of The Beat trying to search an area between itself and the nearest player, instead of wandering into a corner and getting stuck

For example, its loop still couldn’t complete if it spawned far away from players. So, I coded it to slowly nudge itself to players to force encounters and complete the loop sooner.

I also fleshed out its encounters. If it spotted a player it would run away, but playtesters said this made it feel scared. So, because I intended players to feel scared of it, I made the enemy temporarily chase after the player it spotted, to give that player a good scare. However, this gave players little time to process what was happening. In its next iteration, the enemy would roar, taunt, and only then chase after players,  to establish it as a threat without making it a cheap jumpscare or scaredy cat.

Video demo of the intended intimidating encounter with The Beat

The Boxer

The Boxer's design intent was to give combat-savvy players a fair fight, as there were very few of these yet in the game. I wanted this enemy to feel different by asking for this otherwise unused skill.

​

But I also wanted this enemy to feel different as a creature. From reading its design notes, I concluded that Lethal Company enemies were not simply pawns in a game level, but intentionally part of an ecosystem. That, mixed with research into gorillas showing how gentle they are, informed my decision to make The Boxer a "gentle giant".

Video demo for the enemy "The Boxer"
LCBeatBoxerMod BoxerEnemy BananaTree.png
The Boxer's palm tree, indicating where it will spawn

Gameplay Loop:

  • If the game determines this enemy will spawn, it will spawn its palm tree "nest" at the start of the day. I reused the game's nest objects to feedforward players to its presence.

  • Then, if it first sees a player, it will stand upright to alert players to its presence.

  • If players get too close or are carrying weapons:

    • It will run to that player, force a weapon into their hands, and start a fight

    • It will throw a series of powerful attacks, but in a predictable pattern and leaves itself open after every attack

  • But if players stay calm and keep their distance:

    • It will crouch down and passively approach

    • This player can then give it up to four items, and it will then carry these items, so players will not be encumbered by their weight

The Boxer's One-Pager, of which the keywords were so strong they informed the entire enemy's design

Designing Combat:
The Boxer's intent revolved around making one-on-one combat challenging enough to be engaging, but predictable enough to feel fair and rewarding.
 

For this, I researched "Punch-Out!!" for the Wii. I noticed that each CPU boxer would always do the same attacks in the same order. This allowed for a low level of entry, because you always know what to expect, but a high skill ceiling, as it allowed the developers to tweak the difficulty parameters of each individual attack and its timing.

BeatBoxer doc research 1.png
Research into Punch-Out!! showing how they can scale difficulty by being completely predictable

I had to take 3D space and player movement into account, negating the possibility for timing between attacks, but otherwise decided to use an identical system.

 

I used ScriptableObjects to lay out an attack’s data, such as time a counterattack will stun the enemy and its Trigger in the Animator. AnimationClips of each attack would then hold data for each hitbox such as damage, knockback, and player death as parameters. And I created an array of these attacks the enemy loops through, creating a predictable attack pattern.


This system reached its intent, as players are now challenged, incentivized, and rewarded for learning this enemy’s patterns, while preferably not getting punched in the skull in the process.

BeatBoxer pics attackData.png
Data for one of The Boxer's attacks, including the AnimationTrigger and AudioClips to ensure consistency
Data for The Boxer's entire sequence of attacks on loop, making it completely predictable
BeatBoxer pics attackSequence.png

Documenting Development:

For The Boxer, I created the same documents as The Beat. But I also started with keeping a devlog, in which I would list changes made across versions and explain why I made said changes.

  • The One-Pager was extremely impactful in deciding this enemy’s direction, because the two Fantasy-words of “nurturing” and “competitive” laid the groundwork for the “gentle giant” personality. With this goal in place, the document answered most questions I had during development, as I could now ask “does this help the enemy reach this specific design intent?”.

BeatBoxer devlog 1.png
Devlog for this mod, to explain and justify to myself why certain decisions were made for the betterment of the mod
  • I would take note of changes made by writing a devlog. This helped me understand decisions better, and was a good exercise in explaining them. For example, when playtesters noted the enemy had too much HP, yet I decided to increase its HP and add a second phase to its fight, I could use this log to explain the lack of flow emerging from simply making the enemy easier, and that splitting the fight into two phases was for the sake of risk-reward.

Video demo of the Boxer switching between a crouched and upright walking animation, and speeding those animations up based on traveled distance

Visualizing It Properly:
The biggest challenge was animating The Boxer, as he gets up-close and personal, and has many different states.

 

For example, its walking animation. If passive, it would walk on all six limbs, but if carrying items or fighting players it would walk upright. I achieved this by setting “Upright” and “Walking” in the Animator.

Additionally, I made the walking animation speed parameters to be influenced by distance traveled, resulting in a seamless transition from crouched to upright to moving slowly to quickly.

BeatBoxer pics animator.png
The state machine of The Boxer: the blob on the left is each attack leading into its standing idle pose, either directly or via a vulnerable animation

And of course, its combat-attacks needed one animation each. This was mostly a matter of just sitting down and making them, and making my life easier by trying to animate the most important, readable keyposes first and cleaning up in-betweens where necessary.

Video demo of all animations of The Beat and The Boxer in-engine

The End Result:

The result is not perfect of course, and the initial model did not support The Boxer’s animations very well, but it’s something I’m still very proud of it, given it was my first attempt at AI and animation.

If you would like to enjoy this mod too, you can download it through the Thunderstore Mod Manager, following this link: Link to the page

LCBeatBoxerMod online listing 2025-04-07.png
The online listing for the LCBeatBoxerMod as of 2025-04-08
bottom of page