Documentation

GensCore

Placeable generators that drop what you tell them to, fully configurable in game.

v1.0.01.14 - 26.2Spigot / PaperFolia supportedReleased

GensCore gives players blocks they place in the world that produce items on a clock. What each one drops, how fast, and what it upgrades into is entirely yours to define.

Generators are a path rather than a ladder. Tiers branch how you lay them out, share one cooldown, and are created and edited from an in game admin hub.

It comes with its own selling side: /sell moves what your generators made, and sell wands carry a multiplier and a use count so you can hand out limited boosts.

What it does

Generators you define

Create a generator, choose the block, the drop, the speed and the price, all from an in game editor rather than a config file.

Tiers as a path

Upgrades branch rather than climbing a single ladder, and every tier shares one cooldown so the timing stays predictable.

Selling built in

A /sell command moves what the generators made, priced per drop, with no shop plugin needed.

Sell wands

Hand out a wand with its own multiplier and a limited number of uses, created straight from an admin command.

Limits from permissions

A limit permission decides how many generators a player may place, largest held wins, with an unlimited node for staff.

Tells you what is broken

A check command reports anything misconfigured, and a self test walks every placeholder so the docs cannot drift from the code.

Installation

Drop GensCore.jar into your server's plugins folder.
Restart the server. The plugin writes its own configuration on first start.
Run /gens admin hub in game to set everything up. There is no file editing step.

iEverything ships in one jar. The shared framework is shaded in, so GensCore does not depend on any other Core plugin and any number of them run side by side.

Optional integrations

All of these are soft dependencies. GensCore loads and runs with none of them installed.

Plugin	What it adds
Vault	Reads or provides the server economy, depending on the mode you choose.
PlaceholderAPI	Registers the placeholder expansion listed below.
ItemsCore	Custom ItemsCore items are understood and displayed properly.
LuckPerms	Permission driven limits resolve for offline players too.

Commands

Generated from the plugin's own command registry at version 1.0.0, so this list cannot drift out of date.

/gensYour generators/generators/gen

Usage

Usage	Permission	Description
/gens	none	Your generators

Subcommands

Usage	Permission	Player only	Description
/gens list	genscore.use	yes	Show the generators you have placed
/gens admin [action] [player] [generator] [amount]	genscore.admin	no	Administration commands

/gens admin actions

Usage	Permission	Description
/gens admin give <player> <generator> [amount]	genscore.admin.give	Give somebody a generator item
/gens admin sellwand <player> [multiplier] [uses]	genscore.admin.wand	Give somebody a sell wand
/gens admin hub	genscore.admin	Open the admin hub
/gens admin generators	genscore.admin.define	Create and edit generators
/gens admin settings	genscore.admin.settings	Edit the settings in game
/gens admin messages	genscore.admin.settings	Edit any player facing message
/gens admin menus	genscore.admin.menus	Edit any menu in game
/gens admin check	genscore.admin	Report anything misconfigured
/gens admin reload	genscore.admin.reload	Reload the configuration

/sellSell what your generators made

Requires genscore.sell

Usage

Usage	Permission	Description
/sell	genscore.sell	Sell what your generators made

Permissions

everyone is granted to all players, operator only to ops, and nobody must be granted explicitly by a permissions plugin.

Node	Default	Description
genscore.*	operator	Grants every genscore permission
genscore.admin	operator	Use the admin commands
genscore.admin.define	operator	Create and edit generators in game
genscore.admin.give	operator	Give a generator item
genscore.admin.menus	operator	Edit the menus in game
genscore.admin.reload	operator	Reload the configuration
genscore.admin.settings	operator	Edit the settings in game
genscore.admin.touch	operator	Pick up and upgrade anybody's generator
genscore.admin.wand	operator	Create sell wands
genscore.limit.<amount>	nobody	Place up to <amount> generators, largest held wins
genscore.menu	everyone	Open the generators screen
genscore.sell	everyone	Sell generator drops with /sell
genscore.unlimited	operator	Place any number of generators
genscore.use	everyone	Place and pick up generators
genscore.wand	everyone	Use a sell wand

Placeholders

Requires PlaceholderAPI. Turn the expansion off with integrations.placeholderapi: false.

Every key below is walked by the plugin's own self test, which fails if one stops resolving, so this list cannot quietly go out of date.

The generator part of a key is the id you gave it, which is also its file name under generators/.

Server wide

These need no player.

Placeholder	Example	Notes
%genscore_generator_count%	2	how many generators are switched on
%genscore_placed_total%	418	every generator standing on the server
%genscore_drops_per_minute%	73	what the clock actually produced last minute
%genscore_name_<generator>%	Cobblestone Generator	display name
%genscore_tiers_<generator>%	4	how many tiers it has
%genscore_price_<generator>%	$2	what one of its drops sells for

Per player

Placeholder	Example	Notes
%genscore_placed%	7	generators this player has standing
%genscore_limit%	10	how many they may place, unlimited shows as an infinity sign
%genscore_placed_<generator>%	3	how many of one kind they have standing
%genscore_speed%	1.50	their current speed multiplier, all sources multiplied

What they return when they cannot answer

A generator id that does not exist gives an empty string.

A per player key with no player is left unresolved, so PlaceholderAPI leaves the text as it is.

The limit key for an offline player gives the configured default, since permissions are not loaded.