| • Minecraft's scripting engine and modding capabilities | |
| • Microsoft's acquisition of Minecraft in 2014 and its impact on development | |
| • The role of JavaScript in Minecraft's scripting engine | |
| • The evolution of Minecraft's game versions, including the Bedrock Edition | |
| • How web tech (JavaScript, React) was chosen for scripting engine instead of traditional game development languages like C++ or Java | |
| • The challenges and limitations of using dynamic libraries on various platforms | |
| • The introduction of TypeScript to the Minecraft team and its impact on development | |
| • The Minecraft modding platform offers various tools and languages for modders to create custom content. | |
| • The platform includes a scripting engine, commands, JSON files, and Molang (a query language) that allow creators to add dynamic behavior to the game. | |
| • Modders can use these tools to control characters, move objects, and programmatic decision-making, among other capabilities. | |
| • Tutorials and sample repositories are available on Learn.Microsoft.com and GitHub to help new modders get started with scripting in Minecraft. | |
| • The platform is accessible across various platforms, including Windows, iOS, Android, and Xbox (with some limitations). | |
| • Community users using scripting on mobile devices and virtual keyboards can lead to unexpected issues with backwards compatibility | |
| • Hyrum's law: APIs will be abused in ways not anticipated by the developers as soon as they're widely used | |
| • Versioning challenges: updating scripting engines without breaking existing code, ensuring backwards compatibility for old and new behaviors | |
| • Minecraft's strict versioning scheme for scripting API, including module dependencies and manifest files with specific versions | |
| • Event-based APIs require careful consideration to prevent unexpected behavior changes | |
| • Rolling out changes to scripting API or infrastructure code involves a structured process, including checks, change logs, and tagging certain updates | |
| • The Minecraft API is self-service, but requires some level of consistency across the ecosystem. | |
| • The team has a component-based model for functionality, which makes it easier to add new APIs. | |
| • The game is constantly being updated with new content, making it a "moving target" for developers. | |
| • The team releases new types to npm every week as part of their preview release process. | |
| • The engineering effort behind Minecraft is huge, with hundreds of people working on various aspects of the game. | |
| • The player base is still growing, but numbers are not specified. | |
| • The team is expanding its reach into new markets, such as Latin America and China. | |
| • Discussion of Minecraft's marketplace and creator economy | |
| • Introduction of add-ons in Bedrock edition | |
| • Platforms for playing Minecraft, including Xbox, Game Pass, and Chromebooks | |
| • History of Minecraft Classic being a Java applet that ran in browser | |
| • Current official support for Minecraft in browser | |
| • Community-created projects to run Minecraft in browser using Java version | |
| • Details on what people are selling in the marketplace, including maps, skins, and add-ons | |
| • Challenges faced by the scripting/modding team, particularly with versioning | |
| • Combining data definitions and scripting for a cohesive developer experience | |
| • Managing consistency and cohesion across different areas of the project | |
| • Dealing with legacy code and backwards compatibility in API surface | |
| • Balancing the need for innovation with the importance of preserving past work | |
| • Handling deprecation and official breaking changes in major updates | |
| • Respecting creators' roles in updating their content to maintain compatibility | |
| • Managing data loss scenarios and the emotional impact on developers and players | |
| • Community involvement in Minecraft development is crucial and has been ongoing for 16 years | |
| • Working on Minecraft allows developers to interact with a passionate community and engage with users at various levels | |
| • The experience of modding Minecraft as a hobby can be full-circle when working professionally on the game | |
| • Game development presents interesting technical challenges, especially due to owning the engine from top to bottom | |
| • Community resources for learning to mod Minecraft include Discord servers and Microsoft's learn.minecraft.com | |
| • Compiling, building, and linking time spent in software development | |
| • Criticism of build steps in software development | |
| • Humorous discussion about inviting guests with differing opinions on the topic for a future debate | |
| • Mention of TypeScript and the distinction between JS Party and TS Party |