Employee access required
This tool is marked employee-only. Sign in with an employee account from the main Omni-Science site to access it.
Time's Up!
Your free time for this tool has been used. Sign in for more time or upgrade to Omni-Pass for unlimited access.
Get Omni-PassBedrock Asset Library

SYSTEM MANUAL
Welcome to the Bedrock Asset Library by Omni-Science. This system parses .mcpack and .mcaddon files, using Manifest Identification to separate Resource Pack (RP) and Behavior Pack (BP) data regardless of folder structure.
Contents.json
contents.json is a file that is used for the game to process the pack files more easily. It is not required to have this file in your pack for the pack to work properly but is recommended for large addons. Its main purpose is allowing files in Marketplace content to be encrypted, however it is also included in the vanilla packs which are not encrypted.
The contents.json file is located at the root of the pack directory, in the same place as the pack's manifest.json. It contains a list of the files that are included in the pack in the form of an array under the content parameter.
Each content entry can contain two parameters:
- path — The path of the file relative to the pack's root directory. This must include the file extension.
- key (optional) — The key used for decrypting a file that has been encrypted.
Textures_List.json
The textures list is Minecraft's way of caching each texture so that it can retrieve it faster than looking through each image in your textures folder. This is especially important when you have an abundance of textures, where Minecraft could potentially mess up and swap textures or even not load them at all.
Minecraft may display a content log warning if you don't have your textures listed in the file. You can ignore it if you have a small amount, but it is recommended that you list the textures anyway.
Any texture! All textures can and should be used in the textures_list.json file for best practice and performance.
The file itself is in RP/textures and is named textures_list.json. The file contains an array of texture paths (file paths in the textures folder excluding extensions such as .texture_set.json and .png).
UI & Scripting
The single file paths found in the Grid UI are useful for ActionForm icons. They also have other uses. Below is an example of use with ActionFormData:
// 1. IMPORTING TOOLS
import { world } from "@minecraft/server";
import { ActionFormData, ActionFormResponse } from "@minecraft/server-ui";
// 2. LISTENING FOR ITEM USE
world.afterEvents.itemUse.subscribe((eventData) => {
// Check if item is a compass
if (eventData.itemStack.typeId === "minecraft:compass") {
showIconMenu(eventData.source);
}
});
// 3. DEFINING THE MENU FUNCTION
function showIconMenu(player) {
const form = new ActionFormData();
form.title("§l§bTravel Shop");
form.body("Use your compass to navigate or buy supplies!");
// Adding Buttons with Icons copied from this tool
form.button("Buy Apple", "textures/items/apple");
form.button("Buy Sword", "textures/items/diamond_sword");
form.button("Buy Armor", "textures/items/iron_chestplate");
form.show(player).then((response) => {
if (response.canceled) return;
if (response.selection === 0) {
player.sendMessage("§aYou purchased an Apple!");
}
else if (response.selection === 1) {
player.sendMessage("§bYou purchased a Sword!");
}
else if (response.selection === 2) {
player.sendMessage("§7You purchased Armor!");
}
});
} Data Privacy & Safety
This application runs entirely within your browser's "Web Worker" environment. No files are EVER uploaded to an external server.
Your data exists only in your device's RAM for the duration of your session. Refreshing the page instantly wipes all loaded data.
SYSTEM IDLE
DROP PACK FILE HERE
Supports .mcpack, .mcaddon, .zip