Questions & Answers
On this page, you will find possible answers for questions you might have regarding issues
Last updated
Was this helpful?
On this page, you will find possible answers for questions you might have regarding issues
Last updated
Was this helpful?
Some features may not work with Bedrock (using Geyser), such as certain actions in the editor due to the lack of a "Shift" option. However, users can still configure settings through the file system. Additionally, opening animations that use heads won't work due to Geyser limitations. In conclusion, while our plugin supports Bedrock versions, it may not function at full potential.
If only ops can access your crates, the issue may be caused by the "spawn-protection" setting in your "server.properties" file. To fix this, set "spawn-protection" to 0. This will prevent interference and allow all players to access the crates as intended. Additionally, it's recommended to use a plugin like WorldGuard to protect specific regions.
If you're using a dynamic resource pack handler like ItemsAdder, Oraxen or another plugin, ensure it properly manages Model Engine models. Issues are not caused by our crates plugin but may arise if custom assets and Model Engine resources are unintentionally combined. Verify that your ItemsAdder contents folder doesn’t contain files related to Model Engine to avoid synchronization issues with custom model data.
Below is a photo of what was happening to one of our customers:
One reason this issue might occur is that you are using a protection plugin, such as WorldGuard, which has the mob spawning set to false in that region. This setting can prevent Model Engine models from loading properly.
The easiest way is to check the .bbmodel file of your crate. If you're using Blockbench, open your model file in the app. In the top right corner, click on the Animate tab. On the left side, you'll see a list of your model's animations, where you can find the animation IDs.
To create a virtual reward, define it as "virtual" during the configuration process. This means the reward will only be for display purposes, and the player won't receive a physical item. Instead, you can use commands to grant benefits or actions, such as giving a voucher or in-game currency. You can also use PlaceholderAPI to set random quantities for these virtual rewards.
In the preview menu, there are two key concepts: "Percentage" and "Your chance" "Percentage" is the value set by the server owner for a specific reward, indicating its likelihood of being obtained. Multiple rewards can share the same percentage, meaning they have an equal chance of being won. "Your chance" refers to the actual probability of a player winning a particular item. For example, if two items are configured with 100% each, the player has a 50% chance of winning either item. "Your chance" will always total 100%.