(4.0.0 - 4.21.1) 1.0.1 (4.0.0 - 4.21.1) 1.0.0 (3.21.0 - 3.25.6) 0.10.4 (3.21.0 - 3.25.6) 0.10.3 (3.21.0 - 3.25.6) 0.10.2 (3.21.0 - 3.25.6) 0.10.1 (3.21.0 - 3.25.6) 0.10.0 (3.21.0 - 3.25.6) 0.9.0 (3.13.0 - 3.25.6) 0.8.3 (3.13.0 - 3.25.6) 0.8.2 (3.13.0 - 3.25.6) 0.8.1 (3.13.0 - 3.25.6) 0.8.0 (3.13.0 - 3.25.6) 0.7.2 (3.13.0 - 3.25.6) 0.7.1 (3.13.0 - 3.25.6) 0.7.0 (3.4.0 - 3.25.6) 0.6.2 (3.4.0 - 3.25.6) 0.6.1 (3.4.0 - 3.25.6) 0.6.0 (3.4.0 - 3.25.6) 0.5.7 (3.4.0 - 3.25.6) 0.5.6 (3.4.0 - 3.25.6) 0.5.5 (3.4.0 - 3.25.6) 0.5.4 (3.4.0 - 3.25.6) 0.5.3 (3.4.0 - 3.25.6) 0.5.2 (3.4.0 - 3.25.6) 0.5.1 (4.0.0 - 4.21.1) 1.0.2 (5.0.0 - 5.16.0) 1.1.0 (5.0.0 - 5.16.0) 1.2.0 (5.0.0 - 5.16.0) 1.2.1 (5.0.0 - 5.16.0) 1.2.2 (5.0.0 - 5.16.0) 1.2.3 (5.0.0 - 5.16.0) 1.2.4
434
Read more on poggitBedcoreProtect is a fast, efficient, data logging and anti-griefing tool for PocketMine servers. Rollback and restore any amount of damage.
...and much more!!
...and the list is still expanding!
The main command is /bedcoreprotect but it accepts the folllowing aliases: /bcp, /core, /co (Main permission: bcp.command.bedcoreprotect)
Quick command overview:
Shortcut commands:
Advanced command overview:
/bcp help
Diplay a list of commands in-game
/bpc inspect
Enable the inspector. Type the command again to disable it. You can also use just "/bcp i"
/bpc menu
Display a graphic interface to simplify the plugin commands usage. You can also use just "/bcp ui"
/bcp rollback u=<user> t=<time> r=<radius> a=<action> b=<blocks> e=<exclude>
Nearly all of the parameters are optional. Shortcut: "/bcp rb".
u=<user> - Specify a user to rollback.
Example: u=Shoghi u=Shoghi,#zombie
t=<time> - Specify the amount of time to rollback.
You can specify weeks,days,hours,minutes, and seconds.
Example: t=4w5d2h7m20s
You can pick and choose time amounts.
Example: t=5d2h
r=<radius> - Specify a radius.
You can use this to only rollback blocks near you.
For example, the following would only rollback damage within 10 blocks of where you are standing: r=10
a=<action> - Restrict the lookup to a certain action.
For example, if you wanted to only rollback blocks placed, you would use a:+block
Here's a list of all the actions:
• a=block (blocks placed/broken)
• a=+block (blocks placed)
• a=-block (blocks broken)
• a=click (player interactions)
• a=container (items taken from or put in chests, etc.)
• a=+container (items put in chests, etc.)
• a=-container (items taken from chests, etc.)
• a=kill (mobs/animals killed)
b=<blocks> - Restrict the rollback to certain block types.
For example, if you wanted to only rollback stone, you would use b=1
You can specify multiple items, such as b=1,5,7
or b=stone,planks,bedrock
You can find a list of block type IDs at https://minecraft.gamepedia.com/Bedrock_Edition_data_values
e=<exclude> - Exclude certain block types from the rollback.
For example, if you don't want TNT to come back during a rollback, you would type e:46
/bpc restore u=<user> t=<time> r=<radius> a=<action> b=<blocks> e=<exclude>
Same parameters as /bcp rollback. Shortcut: "/bcp rs".
Restoring can be used to undo rollbacks.
/bcp lookup u=<user> t=<time> r=<radius> a=<action> b=<blocks> e=<exclude>
Search through block data using the same parameters as /bcp rollback. Shortcut: "/bcp l".
If multiple pages are returned, use the command "/bcp lookup <page>" to switch pages.
To change the number of lines displayed on a page, use the command "/bcp lookup <page>:<lines>".
For example, "/bcp l 1:10" will return 10 lines of data, starting at the first page.
/bcp purge t=<time>
Purge old block data. Useful for freeing up space on your HDD if you don't need the older data.
For example, "/co purge t:30d" will delete all data older than one month, and only keep the last 30 days of data.
I found a bug, where can I report it?
You can report here by clicking button "Get Started" on Bug report.
Where can I request a new feature?
You can ask a new feature here by clicking button "Get Started" on Feature request.
If you are upgrading the plugin from old versions to v0.5.x, you need to delete the database (bedcore_database.db file if you are using SQLite) and the configuration file (config.yml) because the plugin could not work as intended.