Proposal: Official Standard Libraries for Bedrock Add-ons

Bedrock add-ons and the Bedrock Scripting API have reached a strong level of maturity, but the ecosystem still lacks shared standard libraries. This causes code fragmentation, duplicated logic, incompatibilities between add-ons, inefficient performance usage, and many bugs caused by repeated or incorrect implementations of common functionality.

I propose creating an official standard library system for Bedrock add-ons, maintained by a small internal team focused exclusively on library development.

This system would allow creators to:

• Import libraries from other developers in a standardized way

• Safely manage dependencies and versions

• Improve compatibility between add-ons

• Reduce duplicated infrastructure code

It is essential that this team operates with technical autonomy, using only public APIs and tools available to all creators, with no privileged engine access or internal-only workflows. This ensures libraries are realistic, reproducible, and representative of real Bedrock capabilities.

The team could maintain official standard libraries (math utilities, physics helpers, rendering optimization abstractions, and performance hinting tools), reducing bugs, fragmentation, and maintenance costs.

This library-first approach enables safe experimentation, creates de facto standards without enforcing them, and helps identify proven patterns for future API improvements, while preserving stability and cross-platform compatibility.