Packages
One scope, four categories.
Install the meta-package for a matching set, or take the layers you need on their own.
Framework
Typed addon API imports, observable state and owned services across addon realms.
Read the docsPersisted documents on dynamic properties.
Read the docsReactive values, signals, derived state and batching.
Read the docsScript-event transport, discovery, RPC, events, state and watched snapshots.
Read the docsUI
JSX screens, forms and containers.
Read the docsThemed components with vanilla Minecraft textures.
Read the docsStatic stacks, top tabs and cross-addon screen navigation.
Read the docsThe layout engine under every screen.
Read the docsContent
Every addon in the world, each with the page it published.
Read the docsSettings in three scopes, and the screens that edit them.
Read the docsIn-game guides authored in MDX.
Read the docsTyped keys, interpolation and plurals, resolved per player.
Read the docsWhat you get
Cross-realm plumbing, already solved.
Six pieces that turn a pile of unrelated behavior packs into one coordinated world.
Runtime discovery
Register once. Every other bedrock-core addon in the world sees you, and you see them, the moment they load.
Typed addon APIs
Import async functions and observable values from addon packages while their implementation runs in the owning addon.
Shared state
A declared shape every realm mirrors locally as a typed tree. Reads are synchronous, writes broadcast a delta.
JSX screens
React-like components for forms and containers. Screens compile ahead of time; only state moves at runtime.
Config, guides and translations
Declare a settings schema, ship an MDX guide and a typed translation bundle; the shared UI renders all three for every addon in the world.
One build chain
Builder compiles guides, localization and screens and bundles scripts. BDS runner executes GameTests on a dedicated server.
In practice
Two addons, one typed API.
Export an API from one addon, import it in another, and show the result in a compiled screen.
- 01
- 02
- 03
Economy exports this module and its manifest through package.json. registerModule publishes the checked API from its owning behavior pack.
import { core, registerModule } from '@bedrock-core/server';
import manifest from '../manifest.json';
const balances = new Map<string, number>();
export const API = {
async getBalance(playerId: string): Promise<number> {
return balances.get(playerId) ?? 100;
},
};
core.register({ manifest, economy: registerModule(API) });
import { core } from '@bedrock-core/server';
import { API } from '@studio/economy';
import { render } from '@bedrock-core/ui';
import type { Player } from '@minecraft/server';
import Shop from '../ui/shop.screen';
import manifest from '../manifest.json';
core.register({ manifest });
async function showBalance(player: Player): Promise<void> {
const balance = await API.getBalance(player.id);
render(<Shop balance={balance} />, player);
}
import { Screen, Text, type JSX } from '@bedrock-core/ui';
import { Card } from '@bedrock-core/ore-styled';
export default function Shop({ balance = 0 }: { balance?: number }): JSX.Element {
return (
<Screen>
<Card>
<Text maxLength={32}>{`Balance: ${balance}`}</Text>
</Card>
</Screen>
);
}
Start with one package.
Pin an exact version, and read the changelog before you upgrade.
