๐Ÿ–ฑ๏ธCommands / Permissions

All of the commands and what they do / permission for each one.

Permissions for certain commands can be modified inside of the config.yml

Tournament commands are separate from the base /fish command.

These are all of the commands in the PyroFishing Plugin.

Fishing Player Commands

Feature

Description

Permission

/fish

Shows the command list

pf.commandslist

/fish menu

Opens the main fishing menu

pf.menu

/fish shop

Opens the fish shop

pf.shop

/fish bag

Opens the fish bag

pf.bag

/fish deliveries

Opens the fish deliveries

pf.deliveries

/fish scales

Opens the fish scales

pf.scales

/fish gut

Opens the gutting station

pf.gut

/fish skills

Opens the skill menu

pf.skills

/fish augment

Opens the augmenter

/fish augments

Lists all of the fish augments

/fish codex

Lists all the fish in the plugin

Stops someone from appearing in the codex.

fish.blockcodex

/fish removedelivery

Delete a delivey without accessing the GUI

/fish boosters

Shows your active boosters

/fish entropy

Shows the players entropy

/fish stats

Shows the players stats

Admin Commands

/fish reload

Reloads the plugin

fish.admin

/fish give

Gives the player custom fish

fish.admin

/fish addentropy

Gives the player entropy

fish.admin

/fish addxp

Gives the player fishing xp

fish.admin

Tournament Player Commands

/ft

Base command for tournaments

/ft info

Shows all tournament types

/ft time

Shows time till next tournament

Tournament Admin Commands

/ft start

Starts a tournament

fish.tournaments

/ft stop

Stops a tournament

fish.tournaments

/ft remove

Removes a player from a tournament

fish.tournaments

Codex Blocker

Stops a user from appearing in the codex.

fish.blockcodex

Break Other Totems

Allows a user to break other players totems

fish.totems.break.other

Small note regarding /ft stopUsingtrueas the second argument will distribute rewards while usingfalsewill not.

Empty permission nodes means there is not a default permission node set for that feature. It may be available for configuration in the config.yml however.

By default - OPs will not appear as the 'first caught' in the codex due to them inhertiently having all permissions by default. Negate the permission to allow them to appear in there.

Last updated