You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Documentation about the /paper command and its subcommands.
5
5
version: 1.21.8
6
6
---
7
7
8
-
This page explains the subcommands of the in-game `/paper` command.
8
+
This page explains all commands which are added by Paper.
9
9
10
-
## chunkinfo
10
+
## Bukkit commands
11
+
12
+
These commands are located under the `bukkit:` namespace.
13
+
14
+
### version (aliases: ver, about)
15
+
16
+
The version command displays the version information about the server, the output may look like this:
17
+
18
+

19
+
20
+
You can also use this command to display version information about specific plugins.
21
+
22
+

23
+
24
+
### plugins (alias: pl)
25
+
26
+
The plugins command displays the list of all loaded plugins. Paper differentiates between two types of
27
+
plugins: **Paper plugins** and **Bukkit plugins**. The difference is generally only relevant to plugin
28
+
developers ([guide to paper-plugin.yml](/paper/dev/getting-started/paper-plugins)). Plugins are marked
29
+
as **green** if no issues occurred whilst enabling them and their functionality can be assumed working.
30
+
Plugins marked **red** failed to load or were disabled. Check the startup logs for more information if
31
+
that happens.
32
+
33
+
Bukkit plugins furthermore have the possibility of being loaded **with legacy support** enabled. These
34
+
are marked with a **yellow star** in front of their name. That usually means the plugin was made for a
35
+
very old version of the game or the plugin author simply forgot to specify a target Minecraft version
36
+
for their plugin.
37
+
38
+
You can click on the plugins' names to display version information about that plugin. The click action
39
+
is equivalent to running `/version <plugin_name>`.
40
+
41
+

42
+
43
+
### help (alias: ?)
44
+
45
+
The help command displays descriptions for all registered commands. It acts
46
+
as a quick reference to both built-in commands and any plugin-added commands.
47
+
48
+
### reload (alias: spigot reload)
49
+
50
+
:::danger[Deprecation]
51
+
52
+
The reload command is deprecated for removal. You should instead restart your server
53
+
if you wish to update your plugins, as the reload is known for causing issues with plugins.
54
+
55
+
If you are looking to reload the Paper configs, you can use [/paper reload](#reload).
56
+
57
+
:::
58
+
59
+
## Performance profiling
60
+
61
+
The `/mspt` and `/tps` commands, whilst working fine, are superseeded by the `/spark` command,
62
+
and you should therefore switch to the `/spark` command instead.
63
+
64
+
### spark
65
+
66
+
The only command you should rely on for performance information is the `/spark` command.
67
+
The spark subcommands are documented [in the dedicated spark wiki](https://spark.lucko.me/docs/Command-Usage).
68
+
69
+
### tps
70
+
71
+
The tps command is a simple command to get the TPS (ticks per second, how often the game loop
72
+
is run per second. The higher, the better. Target TPS is 20.0) from the past 1, 5, and 15 minutes.
73
+
74
+
### mspt
75
+
76
+
The mspt command is another simple command to get the average, min, and max MSPT (milliseconds per tick, how much time
77
+
a tick takes. The lower, the better. MSPT should be below 50 for 20 TPS) of the server from the last 5, 10, and 60 seconds.
78
+
79
+
### timings
80
+
81
+
:::danger[Deprecation]
82
+
83
+
The timings command is deprecated for removal. You should instead use the [spark command](#spark) as a replacement.
84
+
85
+
More information can be viewed here: https://github.com/PaperMC/Paper/discussions/10565.
86
+
87
+
:::
88
+
89
+
## restart
90
+
91
+
The `/restart` command is part of Spigot's restart mechanism, which makes the server restart when it crashes
92
+
or the command is run manually.
93
+
94
+
:::note
95
+
96
+
For help setting up the restart script, see
97
+
[this gist by Prof_Bloodstone](https://gist.github.com/Prof-Bloodstone/6367eb4016eaf9d1646a88772cdbbac5).
98
+
99
+
:::
100
+
101
+
## paper
102
+
This section is dedicated to the subcommands of the in-game `/paper` command.
103
+
104
+
### chunkinfo
11
105
The `/paper chunkinfo [<worldname>]` command is used for displaying information about loaded chunks in a world.
12
106
You can specify the world to get info about with the `[<worldname>]` argument. If you set it to `*` or leave it
13
107
out, it will list information for all worlds.
@@ -21,28 +115,28 @@ A more complete documentation may be found in the [Minecraft wiki](https://minec
21
115
-`Block Ticking` All game aspects work as expected, except that entities are not spawned naturally or ticked, but still accessible. Also called **lazy chunks**.
22
116
-`Entity Ticking` The chunk is being ticked fully.
23
117
24
-
## debug
118
+
###debug
25
119
The `/paper debug <chunks>` command is used to dump information about all currently loaded chunks to a file. The content
26
120
of this file is generally irrelevant for most server admins and is intended to be used by developers.
27
121
28
-
## dumpitem
122
+
###dumpitem
29
123
The `/paper dumpitem [all]` command can be used to retrieve the data component representation of your currently held
30
124
item. Simply running `/paper dumpitem` will yield the item data, which you can use to represent this item in
31
125
commands which expect an item argument. `/paper dumpitem all` yields the **full data component representation**,
32
126
including default data components you do not have to explicitly declare.
33
127
34
-
## dumplisteners
128
+
###dumplisteners
35
129
The `/paper dumplisteners toFile|<className>` command is primarily intended for developers trying to figure out why
36
130
their event handlers might not be working as expected. Using `/paper dumplisteners toFile` will write all
37
131
currently registered event handlers to a file, whilst `/paper dumplisteners <className>` will print the registered
38
132
event handlers only for the specific event.
39
133
40
-
## dumpplugins
134
+
###dumpplugins
41
135
The `/paper dumpplugins` command is intended for developers trying to figure out issues with their dependencies or
42
136
loading order in relation to other plugins. It can also be used to debug bootstrapper providers, general load order,
43
137
and listing class loaders for the plugins.
44
138
45
-
## entity
139
+
###entity
46
140
The `/paper entity list [<filter>] [<world>]` command can be used to list all currently ticking entities.
47
141
48
142
The `[<filter>]` argument is used to filter the listed entities types and acts similar to a **regular expression**:
@@ -67,17 +161,17 @@ Total Ticking: -78, Total Non-Ticking: 92
67
161
68
162
The comment at the end already clearly describes the purpose of the numbers.
69
163
70
-
## fixlight
164
+
###fixlight
71
165
The `/paper fixlight` command is a simple command to trigger a full re-calculation of the light map of all currently
72
166
loaded chunks. This can be used to fix any lighting issues which commonly occur with plugins like WorldEdit.
73
167
74
-
## heap
168
+
###heap
75
169
The `/paper heap` is a developer debug command to dump the current JVM heap to a `.hprof` file, which can be analyzed
76
170
to detect to amount of memory used by certain objects. The output file can be rather big, so having a bit of free
77
171
space on your disk is recommended before running this command (as a general rule, the file is usually smaller
78
172
than the currently used memory. You can check the memory consumption using the `/spark healthreport` command).
79
173
80
-
## holderinfo
174
+
###holderinfo
81
175
The `/paper holderinfo [<world>]` command is used to gather the number of different chunks currently held in memory.
82
176
83
177
The `[<world>]` argument can be used to define the world to get the chunk holder information for. Leave blank to
@@ -91,22 +185,22 @@ In general, the types have the following meanings:
91
185
-`Proto` A "prototype" chunk, which is a fully working chunk loaded in memory, but which is not currently placed in the world.
92
186
-`Full` Represents the number of chunks currently placed in the world.
93
187
94
-
## mobcaps
188
+
###mobcaps
95
189
Not to be confused with the [playermobcaps](#playermobcaps) subcommand, the `/paper mobcaps [<world>]` command displays
96
190
the **global** mob caps for all players in a world. The `[<world>]` argument defaults to the overworld and
97
191
can be set to retrieve the mob caps for other worlds as well. The command also lists the number of
98
192
chunks in which mobs can spawn.
99
193
100
-
## playermobcaps
194
+
###playermobcaps
101
195
The `/paper playermobcaps [<player>]` command is used to list the local mob caps for a specific player. The `[<player>]`
102
196
argument defaults to the player, who ran the command, if one exists.
103
197
104
-
## reload
198
+
###reload
105
199
The `/paper reload` command is an unsupported command which allows for runtime Paper-config reloading. If you get any issues
106
200
after using this command, please make sure to reproduce this on a freshly-started server before asking for help or
107
201
reporting it. Do not that this command **does not** reload non-Paper configs, like the `spigot.yml`.
108
202
109
-
## syncloadinfo
203
+
###syncloadinfo
110
204
The `/paper syncloadinfo [clear]` command requires the `-Dpaper.debug-sync-loads=true` JVM flag to be explicitly set
111
205
before running the command. The command was historically used for debugging purposes during Paper development, but
112
206
the mechanism behind the command is currently unused, meaning that the written file will **always** look
@@ -120,5 +214,5 @@ like this:
120
214
121
215
Outside of checking for whether the command is allowed to be run, the JVM flag is otherwise unused.
122
216
123
-
## version
217
+
###version
124
218
The `/paper version` command is an alias to the standard `/version` command.
0 commit comments