This is the repository for bridge. v2.0.0.
- Visit https://editor.bridge-core.app/ with a supported browser. (We recommend the new Edge based on Chromium)
- Click the install icon that appears inside of the URL bar.
- bridge. v2 is now installed to your system. You can continue with the guided setup process.
For more help on how to get started, please refer to our getting started guide.
bridge. v2 comes with a gorgeous redesign of all UI elements. This gives bridge. v2 a fresh new look and increases the usability of our UI.
Our new pack explorer combines all pack types into a single, color-coded sidebar area.
Presets are now at the front and center of creating files. Presets allow users to quickly create all files necessary to get a feature working in game. They are perfect for e.g. quickly setting up a new entity, block or item. You can also see that all window sidebars now have an updated look and all content windows now offer the ability to quickly search for things.
Our new extension store also received a visual overhaul and some significant functionality changes to make it easier to keep extensions up to date, disabling/enabling installed extensions and exploring the catalogue.
bridge. v2 now supports creating skin packs and world templates in addition to behavior and resource packs. We have also published an extension called "WorldHub" which allows creators to add multiple worlds to a project & pulling/pushing them from/to the com.mojang folder.
bridge. v2 moves projects out of the com.mojang directory by default. Additionally, all packs that belong to a project can be found inside of a single folder. This allows for very easy integration with version control systems like git and makes it easier to work on the project with other editors. A typical v2 project looks like this:
-- My Project/
--- .bridge/
--- BP/
---- ...
---- manifest.json
--- RP/
---- ...
---- manifest.json
--- SP/
---- ...
---- manifest.json
--- config.json
Even though bridge. v2 no longer stores your project inside of the com.mojang folder, you still get the same seamless development experience if you have setup com.mojang syncing by dragging the folder onto bridge. v2. Upon making changes to the project folder, bridge. will re-compile the file and move it to Minecraft for testing. Because this process is fully automatic, you should never manually work on the add-on inside of the com.mojang folder because any changes might get overwritten. Always work with the project folder!
When you make changes to your project outside of bridge., you can refresh the project and bridge. will pick up any changes made with external editors and update the com.mojang output accordingly. This also works with file deletions & renames.
Our compiler generally has two modes: "dev" and "build". The procedure described above always happens inside of "dev" mode. It is optimized for delivering fast & correct updates to all files that need to change whenever a source file inside of the dependency tree changes. The "build" mode compiles a full build that is ready for production inside of the "project/builds/dist/" folder. Some compiler plugins such as AnyLanguage are designed to only work inside of this compiler mode.
bridge. v2 finally allows developers to freely switch between editing JSON files as text or in a dedicated tree editor that prevents newer users from making syntax mistakes. We also added a global find & replace system and live previews of files while your are working on them.
We are using Monaco to provide the same incredible editing experience VS Code provides and we ship auto-completions & validations for all of Minecraft's JSON files.
Our new tree editor features support for multiple selections, direct/more natural keybindings (e.g. "Del" instead of "Ctrl + Del") and makes use of the same new JSON schemas our text editor uses for its auto-completions. We are looking to add better (more Minecraft-y) syntax highlighting to both our text editor and tree editor in the future.
bridge. v2 ships with the ability to preview files while you edit them. This allows developers to find the perfect seat positions & collision/hit boxes without needing to jump into Minecraft. We support previewing particles, entities (components, models, particles & animations) and blocks (components & models).
This was one of the most requested features for bridge. v1. It proofed to be technically difficult to implement previously because of the cache system that was in place for the old editor. With our new codebase, we were finally able to add a global find & replace system!
We are proud to already feature some fantastic new extensions on bridge. v2's extension store.
- We have compiler plugins for automatically generating the "texture_list.json" file for production builds or automatically generating all lang files based on the "en_US.lang" file
- A lot of themes are already available for bridge. v2
- @aexer0e's fantastic "Compact Prettier" changes the default "format on save" formatter to produce more compact output
- There are fantastic UI extensions such as @jasonjgardner's texture set generator, the MoLang Playground or @aexer0e's Table2 extension for displaying & editing Google Docs Tables inside of bridge.
