Brigadier for Lethal Company

Language available in README: [한국어 (대한민국)] [English (US)]

This is a mod that ports Brigadier.NET to Lethal Company.

Explanation

It has really basic commands and execute commands built in.
So you can use Vector3 arguments, and of course you can use relative coordinates like ~ ~ ~

You can also use entity selectors like Minecraft's @e[type=enemy] @s

Selector Description

@a : All Players
@e : All Entities (Player, Enemy, Item) (Please note that items in your inventory are also considered items.)
@s : Oneself
@p : Closest player other than yourself
@n : Closest entity other than itself
@r : One random player among all players


[type=] Entity Type (Can also be used as a negation by adding '!' in front)\

Example :
@e[type=!player,type=!item] (Can be used like @e[type=!player|!item])
@e[type=player|enemy] (Brings only players and enemies)

Entity Type : player, enemy, anomaly, item


[name=] Entity Name (Can also be used as a negation by adding '!' in front)
Example : @e[name=Rumi727|jester|"S!p?e!c?i!a?l characters and spaces can be enclosed in \""]
(Retrieve only entities with names Rumi727 or jester or S!p?e!c?i!a?l characters and spaces can be enclosed in ")


[distance=] Distance
Example : @e[type=!player,distance=..10] Gets all entities within a 10m radius, excluding players.


[limit=] Limit
Example : @e[limit=1] Get the first entity among all entities


[death=false] Select only undead entities
[death=true] Select only dead entities


[sort=near] Sort by closest
[sort=far] Sort by furthest
[sort=random] Random sort

I understand completely.
The selector code is incredibly messy and has become a tangled mess of spaghetti.
It was created without reverse-engineering the Minecraft source code, and back when I first wrote it, I wasn't really at the level where I could effectively leverage AI to help me.
So, yeah... that's how it ended up.
Honestly, I just can't be bothered to fix it at this point...

Add custom commands

If you inherit ServerCommand
An instance is created at the NetworkManager.OnServerStarted stage and the Register method is automatically called.

You can register the node to ServerCommand.dispatcher in the Register method.

The argument type can be accessed through the LethalArguments class.

If you want to get the current command's position or rotation value,
you can refer to the values ​​stored in Command Source.

For detailed usage, please refer to the Brigadier.NET document. Although it's Java, the Fabric documentation might also help...lol

The ThunderStore release also includes XML documentation, so you may find that helpful as well.

2.1.0

• Changed the player identification method from using GameObjects to using the RpcParams approach. (In other words, it means it was previously possible to spoof the sender on the client side...)
• Players without Operator permissions can no longer use any cheat commands that affect game balance.
• Added op and deop commands to grant or revoke Operator privileges.
  • The server owner can use the op command even without being an operator.

2.0.1

• Modified README and CHANGELOG

2.0.0

• Fixed a bug that was not working starting from a specific version.
• Not compatible with previous versions
• Autocomplete is supported with Tab and arrow keys.

1.0.3

Resolved a conflict with the LLC mod

1.0.2

Fix execute positioned command
Fix execute rotated command

1.0.1

Update README

1.0.0

First release