- 18,529 views, 8 today
- 6,619 downloads, 1 today
776
Use this framework to implement "Minecraft, But ?????" scenarios.
You must've seen the concept before. "Minecraft, but item drops are multiplied", "Minecraft, but you have to walk in a straight line", "Minecraft, but you cannot touch the floor", do I need to go on? This data pack is a framework that you can use to quickly build your own "Minecraft, But ?????" scenarios. Besides offering an easy-to-use and powerful connections, the common platform avoids all data packs being enabled at once and will randomly choose one every 5 minutes (by default)! This allows for a pleasant experience, where the user has increased variety and content and the creators have increased exposure. Of course, creators will be given appropriate credit in chat ever time their scenario gets picked.
I found a submission containing scenarios, how do I play?
- Click the download button on this page, download the zip file and extract the Framework folder inside to your datapacks folder. You can ignore any other folders/files.
- Click the download button on the submission page of the scenario. You should be able to just download it straight to the datapacks folder, but be aware that some creators might put different instructions on their submission page.
- Create a runner structure. Each runner structure represents a timer, place multiple for multiple scenarios at once. However, it's recommended to start with one. Also make sure it's placed in an always loaded area (e.g. world spawn).
/function bertiecrafter:mcb/runner - Use the button on the structure to open a menu containing buttons for setting the timer, starting the next scenario or destroying the runner. In vanilla Minecraft, it should highlight the runner with an invisible glowing slime. This slime might be visible when using optifine :|
- Uninstall by running /function bertiecrafter:mcb/uninstall (after removing runners from the menu).
Instructions
- Download zip file and extract both the Framework and the example data pack folders to your datapacks folder. Don't alter the framework data pack during development.
- Rename the example data pack ("Minecraft But") folder to your own name.
- Rename the data/steve folder inside. We will later refer to the new name as <namespace>.
- Go into data/bertiecrafter/tags/functions and for each of the files, rename "steve" to <namespace>.
- The downloaded zip file also contains a config file for the Data Pack Checker in case you want to check if you're using the framework as intended. You can download rule files here.Rules that are automatically checked by the Data Pack Checker
- Create datapack for version 1.16.5 and up (version identifier 6).
- No dangerous or global commands allowed (ban/kick/op/gamerule/worldborder/etc, see the configuration file for the full list.)
- The functions registered in uninstall/register/load tags cannot have visible output (chat, sound, particles).
- The functions registered in the register tag can only have commands that match the template. No other commands allowed.
- Besides the specified tags, the bertiecrafter/minecraft/steve namespaces cannot be used, use a namespace you own (like your IGN) instead. This also means that you cannot register functions in #minecraft:load and #minecraft:tick.
- Besides commands referenced by #bertiecrafter:mcb/register, in-game resources cannot have "bcmcb" prefix or "bertiecrafter" namespace.
- Tags cannot be specified in a way that it overrides the contents of other tags. (The "replace" key)
- All functions must start with a comment beginning with "#As/At" that describe where (~ ~ ~) and as what (@s) a function executes. Two distinct comments starting with "#As" and "#At" are allowed too.
- The uninstall function must contain a removal command for all detected commands that create something. (E.g. you must provide a "/scoreboard objectives remove" command for every "/scoreboard objectives add")
- You must prefix all in-game resources (objectives, tags, bossbars, teams, etc) to prevent clashes. (e.g. "svmcb_" for "Steve's Minecraft But")
- All resources (functions, tags, structures) must be inside a mcb folder. That means that most function commands will look something like "/function my_namespace:mcb/my_function".
- The pack.mcmeta file must specify version 6.
- In the off-chance of 1.17 being released during the event, a rule will be released that will highlight which commands you need to change and where.
- Go into <namespace>/functions and implement the functions as follows:Load
All non-visible setup that should only be executed once, across multiple occurrences of any scenario. (Equivalent to #minecraft:load) UninstallAny commands necessary to clean up when this data pack gets uninstalled. Should roughly be the opposite of Load. RegisterContains a template command that can be copied as much as you like, one for each possible scenario. Each command specifies a title, description, author and function references.
One command has already been added. It contains /function commands referencing the functions below, feel free to rename the mentioned function files.StartAll setup that needs to be repeated every time the scenario starts. TickMost logic should be implemented here. Similar to #minecraft:tick, but only runs while the scenario is active. StopAny commands necessary to clean up any visible left overs from your scenario, so that your scenario is hidden in every way possible while it isn't active. -The above are starting points called by the framework. You are free to create any amount of other files that a data pack supports. - Don't forget to create runner structures (see instructions at the top).
- The framework does contain the Yellow Shulker Box loot table for inventory manipulation, so you don't have to include it.
- When publishing, make sure to explain that users need this framework. Add a link to this page, do not include the framework in your data pack or submission download.
The event
This framework was used as part of an event. View all entries here.
Thank you Moggla and Chimerabot for testing the framework!
Install Instructions
This is a datapack, but it has special instructions. Follow the steps in the description above =)
I encountered a bug! What do I do now?
I test all my creations, but bugs happen no matter how long you test something. Whenever someone experiences a bug, I do my best to fix the issue. You can help me by providing any useful information. You can never give me enough information, but please send it in a DM instead of placing it in the comments. You can still place a one-liner in the comments stating the issue to make the community aware, but that alone isn't enough to help me fix the issue.
- Checklist: Are you using the right version? Did you do /reload after dropping the datapack in? After /reload, does the datapack show up green in /datapack list?
- What is the issue? Does the datapack not seem to be working at all or is there a specific feature you are having issues with?
- What happened? Please give me all the steps needed to reproduce the issue. The faster I can experience it, the faster I can solve it.
- What did you expect to happen instead? This helps me understand your point of view and determine if the issue described is actually the issue I need to fix. The bug you are experiencing could just be a side effect of something else that doesn't behave as expected.
| Compatibility | Minecraft 1.16 |
| Tags |
1 Update Logs
Automatic disable commandblock output. : by Bertiecrafter 03/14/2021 11:08:11 amMar 14th, 2021
Command block output is now disabled on load, this does not change the way data packs interact with frameworks.
Thanks One_Nose for telling me.
Also the upload button is a bit broken, so it's a MediaFire link for now...
Thanks One_Nose for telling me.
Also the upload button is a bit broken, so it's a MediaFire link for now...
tools/tracking
4967622
119
minecraft-but-framework
ApparentlySkilled
MistFaller
BlissyMissy
Sophisticated_Trashcan
PixelCraft__YT
PrincessLuna16
GalaxyCat24
Hut
Create an account or sign in to comment.
Once you installed the framework and at least one scenario data pack AND spawned the runner (see instructions at the start of the description), you should see messages appear in chat when a scenario starts and ends.
If not, check if you did /reload, are on the right version and on a vanilla server (or single player of course).