AbyssCore is a staff and server-management mod, and the shared library behind the Abyss mods. It gives server staff an in-game menu and commands to moderate players, protect areas and run events, and it gives other mods a ready-made API for permissions, networking, synced player data, screen effects and Abyss-styled screens.
It runs on NeoForge 1.21.1 and Forge 1.20.1.
Why use it
- One staff menu instead of a pile of commands. Moderators open a single screen to manage players, titles, help requests, regions and dimensions.
- Real staff roles without giving out OP. Moderators get the tools they need; only operators get the dangerous ones.
- Region protection that is simple to set up. Mark an area, add tags like
no_buildorkeep_inventory, done. - For mod developers: permissions, packets, synced player data, overlays and a GUI toolkit that work the same on both loaders, so you write the code once.
Features for server staff
Permissions. Three levels: Player, Moderator and Admin. Every server operator is Admin automatically. Moderators are granted with /abysscore permission grant <player> MODERATOR and do not need OP. Moderators only see the parts of the menu they are allowed to use.
Staff menu (/abysscore). Players, titles, vanish, regions, dimensions, help requests, bulk commands and key binds in one screen.
Player tools. God mode, blind (black screen and frozen view), and vanish with per-player exceptions (needs Vanishmod).
Regions. Create areas from two corners or your WorldEdit selection, then add tags to them:
no_build,no_interact,no_fly,no_friendlyfire,no_hunger,no_tpno_mobspawning_hostile,no_mobspawning_pacificno_entry, with an optional tag that lets chosen players inkeep_inventory: players who die inside keep their items and XP
Dimensions. Create, load and teleport between custom dimensions, with per-dimension gamerules.
Titles. Save title and subtitle presets and send them to everyone, a team, a tag or one player.
Help requests. Players use /abysshelp <reason>; staff see the request in the menu and accept it.
Bulk commands and key binds. Save a list of commands under one name, run it with /abysscore run <name>, or bind it to one of nine keys.
Chat lock. Mute chat for everyone except staff during events.
Corruption. A 0–100 value per player with a HUD bar, used by other Abyss mods. Players can hide the bar with /corruptionhud.
Features for mod developers
- Shared permission checks for commands, packet handlers and screens
- One networking API for both loaders: plain record packets, one channel per mod
- Per-player data that is saved, kept on death and synced to the client
- Screen tints and vignettes tied to effects, damage types or code
- Continuous effects that never flicker, and custom damage types
- An Abyss-styled GUI toolkit: panel screens with tabs, widgets, layouts, dialogs and movable HUDs that players can rearrange in game
- GeckoLib base classes for animated items and entities
Full documentation with examples: https://github.com/Gugas749/AbyssCore-MultiLoader/wiki
Before you install
- Install AbyssCore on both the server and every client. It adds screens, a HUD and key binds, and clients cannot join a server running a different AbyssCore version.
- Required: GeckoLib.
- Optional, used automatically when installed: Vanishmod (vanish), WorldEdit (regions from your selection), Waystones (blocked in
no_tpregions). - Settings and saved data are in the
config/abysscore/folder.
Data sent outside the game
AbyssCore can send help requests to a Discord channel. This is off by default. It only happens if the server owner turns on help_webhook_enabled and sets help_webhook_url in config/abysscore/abysscore-server.json. When it is on, each /abysshelp request sends the player's name, UUID and the reason they typed to that Discord webhook. Nothing else is sent anywhere.
License
BSD 3-Clause License.