Free tools Windows power users keep installed
One-click scans. No signup required.
Use CoreProtect as a narrowly scoped audit-and-recovery process: look up the player’s activity during the death window, determine whether the loss was logged as an inventory transaction (a:inventory) or an item-entity action (a:item), preview the rollback, and only then apply it. Recovery is possible only while the relevant history remains retained and you have the separate permissions required for lookup, rollback, and restore.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
What CoreProtect can recover after a death
CoreProtect records server actions as history rather than taking a simple, automatic snapshot of every player inventory. That distinction determines whether a death recovery will work. You are reconstructing a recorded action inside a selected time and location scope, not loading a universal “inventory before death” file.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchA successful recovery normally has four stages: identify the incident, classify the logged action, preview a narrowly scoped rollback, and apply the verified command. If you skip the lookup and run a broad rollback, you can alter unrelated activity in the same area or time period.
CoreProtect documents rollback and restore as separate operations. Rollback applies a change to undo matching recorded actions; restore can undo a CoreProtect rollback or restore player actions. A restore still depends on the original history being available, so it cannot replace a world backup when the underlying data has already been removed.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Requirements before you run a command
- CoreProtect must be installed and running. If the plugin is stopped, newly occurring actions will not be recorded, and commands may be unavailable.
- The affected world must have retained history. Purged or never-recorded events cannot be reconstructed by a later command.
- You need the appropriate permission for each operation. Lookup, rollback, and restore permissions are separate; being able to inspect history does not automatically grant permission to change it.
- Record the incident details. Write down the exact player name, world, approximate death time, location, and what the player reports missing. Those details become your filters and your audit trail.
Do not begin with a global command. A death recovery should identify the smallest practical player, time, location, world, and action scope before anything is changed.
Choose the right action filter
a:inventory: inventory additions and removals
The a:inventory action covers items added to or removed from player inventories. It is the right starting point when the relevant evidence is an inventory transaction, such as items entering or leaving the player’s inventory in the recorded history.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
a:item: item entities and player item activity
The a:item action covers items dropped, thrown, picked up, deposited, or withdrawn by players. A death can create item entities in the world, so an inventory-only query may not show the whole incident. Investigate a:item as well when the loss involved dropped items or subsequent pickup, deposit, or withdrawal activity.
Why a death may require both
The player’s inventory state and the world’s item entities are different parts of the event. Start with the category that matches the reported symptom, then check the other category when the first result is incomplete. For example, a player who died and dropped equipment may have relevant records under a:item, while a later pickup or inventory movement can appear in the inventory history.
Step-by-step recovery workflow
1. Confirm the recording environment
Verify that CoreProtect is enabled on the server and that you are working in the world where the death occurred. Confirm that the incident falls inside the period for which the server still retains CoreProtect history. If the event predates retention or logging was disabled, commands cannot recreate it.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
2. Run a focused lookup
Begin with a lookup, not a rollback. A basic inventory query is:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems/co lookup u:Player t:3d a:inventoryReplace Player with the exact player name and adjust the time window to the shortest period that includes the death. The documented lookup searches inventory transactions for that user in the selected window. If items were dropped or moved as entities, run an equivalent lookup using a:item.
Lookup has no default radius. That means you should supply a location scope when your server’s command interface and incident details allow it, or otherwise make the player, time, and world filters as specific as possible. A lookup result is evidence for choosing the next command; it does not itself change the world.
3. Narrow the incident
Use the actual player name, the shortest credible time range, the affected world, and a radius that covers the death site without sweeping in unrelated activity. A one-minute or ten-minute window around a known death is safer than several days when the timestamp is available. If the time is uncertain, widen the lookup first, inspect the results, and then tighten the rollback scope.
Separate multiple deaths. If the player died twice during the same broad time period, do not treat the entire interval as one incident. Identify which records correspond to the reported loss before preparing a rollback.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
4. Preview the rollback
Use the same filters in preview mode. For example:
/co rollback u:Player t:10m r:20 a:inventory #previewThe preview should show the number of matching changes and their locations without applying them. Check that the count, player, time, radius, world, and action category describe the death you are repairing. If the preview includes unrelated activity, stop and tighten the filters. If it returns nothing, try the other action category or correct the time and location rather than removing safeguards.
5. Apply the verified rollback
After the preview matches the incident, run the same command without #preview:
/co rollback u:Player t:10m r:20 a:inventoryKeep the exact command, operator, timestamp, and preview result in your incident record. If the death involved item entities, use the verified a:item scope instead, or handle each verified scope separately rather than replacing both with an unnecessarily broad command.
6. Verify the result in game
Have the player check the relevant inventory or recovery location. Confirm that the intended items returned and that unrelated players, containers, or nearby builds were not altered. If the result is incomplete, do not immediately repeat the rollback with a wider radius. First perform another lookup for the missing action category, time segment, or location.
7. Reverse an incorrect rollback when necessary
If a rollback affected the wrong records, use the corresponding /co restore scope to reverse that CoreProtect change. Restoration requires the history needed to identify the original state. If that history is missing, a restore cannot substitute for a world backup.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
CoreProtect command facts at a glance
| Command or parameter | Purpose | Recovery implication |
|---|---|---|
/co lookup |
Investigates recorded activity without applying a rollback. | Use it first to identify the death’s records and choose the correct action filter. |
/co rollback |
Applies a change to matching recorded activity. | Run with the narrowest verified scope; preview with #preview first. |
/co restore |
Reverses a CoreProtect rollback or restores player actions. | It depends on retained history and is not a substitute for a world backup. |
u:Player |
Limits the command to a user. | Use the exact affected player rather than a global user scope. |
t:10m, t:3d |
Limits the command to a time window. | Start with the shortest window that contains the death. |
r:20 |
Limits a command to a radius. | Choose a radius that covers the incident but excludes nearby activity. |
a:inventory |
Matches items added to or removed from player inventories. | Use for inventory transactions. |
a:item |
Matches items dropped, thrown, picked up, deposited, or withdrawn by players. | Use when item entities or player item movement are part of the loss. |
#preview |
Shows what a rollback would match without applying it. | Required safety check before removing the preview marker and executing. |
CoreProtect’s documented rollback behavior applies a default radius of 10 when no radius is supplied. Because a recovery incident should be deliberate, set the radius explicitly instead of relying on that default. Lookup has no default radius, so do not assume its results are location-limited.
Recovery playbooks for common death reports
The player died and items were visibly scattered
- Use a short lookup window around the death with
a:item. - Check whether the records show the drop and any later pickup, deposit, or withdrawal.
- Preview a rollback with the player, time, radius, world, and
a:itemfilters. - Apply only after the preview identifies the reported drop area.
Check a:inventory too if the player says some items were restored while others are missing, because the two categories represent different logged activity.
The player reports an inventory transaction, not a visible drop
- Look up the player with
a:inventoryin the death window. - Use the records to identify the relevant location and time.
- Preview the matching inventory rollback at that scope.
- Apply and verify the player’s inventory.
The death involved both dropped items and later movement
Investigate both categories separately. A single action filter can miss records represented by the other category. Preview each proposed scope independently, document both commands, and apply only the commands whose previews correspond to the reported incident.
The player name or death time is uncertain
Do not compensate for uncertainty with a global rollback. Confirm the exact account name and ask for the narrowest usable time estimate. Begin with a lookup over a wider window, then reduce the interval and radius after the matching records are visible.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to read a preview safely
A preview is useful only when its matches make sense for the incident. Check these dimensions before execution:
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
- User: Every match should belong to the affected player, not merely occur near them.
- Time: The records should bracket the death and exclude routine activity before or after it.
- Location: The returned locations should be at the death site or the documented item path.
- Action: The category should correspond to inventory transactions or item activity as reported.
- Count: An unexpectedly large count is a warning to tighten the scope; a zero count means the filters or retained history may not match.
Do not treat a matching player name alone as proof. A player can have many ordinary inventory or item actions during a multi-day window, and a rollback would affect every matching record inside that scope.
When recovery fails
No results from lookup
Check the exact player name, world, time window, and action category. Widen the lookup interval cautiously if the death time is uncertain, then narrow it again after identifying the event. If neither a:inventory nor a:item returns the incident, the event may not have been logged or may have passed the server’s retention period.
The preview count is too large
Reduce the time window, set a smaller radius, confirm the player filter, and ensure you are in the affected world. Do not apply a large preview simply because it includes the desired death; unrelated actions could be changed as well.
The preview is empty but the player insists items were dropped
Try a:item if you started with a:inventory, and inspect both the death location and the time immediately afterward. Dropped, picked-up, deposited, and withdrawn items are represented by the item-action category, not necessarily by the inventory category.
The rollback changed the wrong area
Stop further commands. Preserve the exact command and preview output, then use the corresponding /co restore scope if the required history is still available. If the original data is unavailable, use the server’s world-backup process rather than assuming another CoreProtect command can reconstruct it.
The command is denied
Ask an administrator to verify the separate permission for the operation you are attempting. Lookup, rollback, and restore are independently permissioned, so successful lookup does not prove that rollback or restore is authorized.
CoreProtect versus other recovery methods
CoreProtect is an action-history system. Other methods solve a different problem, and choosing between them depends on what evidence remains.
| Recovery method | What it preserves | Can it work after CoreProtect history is purged? | Scope and reversibility |
|---|---|---|---|
| CoreProtect | Recorded player and world actions, including inventory and item activity. | No. Purged or never-recorded history cannot be queried. | Precise user, time, radius, world, and action filters; rollback can be reversed with restore while the needed history remains. |
| Dedicated inventory-backup plugin | Point-in-time inventory snapshots, subject to that plugin’s own retention and configuration. | Potentially, if its snapshot predates the death and is still retained; capabilities depend on the specific plugin. | Snapshot-based recovery may be less suited to reconstructing nearby item entities or individual transactions. |
| World backup | A broader point-in-time copy of the world and server data. | Yes, if a suitable backup exists. | Can restore more than one player’s items and may overwrite legitimate changes made after the backup; it is not a transaction-level correction. |
Use CoreProtect when the event is retained and can be isolated safely. Use a world backup when the required history is missing or the incident extends beyond recorded actions, accepting the wider impact of a backup restore.
Quick Recap
Administrative checklist
- Confirm CoreProtect is active and logging the affected world.
- Confirm the incident’s player, world, location, and approximate time.
- Run
/co lookupbefore any rollback. - Check
a:inventoryanda:itemwhen the death involved both inventory changes and dropped entities. - Set the player, time, radius, world, and action scope explicitly; do not rely on rollback’s default radius of 10.
- Run a preview and review its count and locations.
- Save the exact approved command and preview result.
- Verify the player’s items after applying the rollback.
- Use the matching
/co restorescope to undo an incorrect rollback when history is still available. - Escalate to a world backup when the relevant history was never recorded or has been purged.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
