The Runtime API exposes everything you could possibly want to access within the Webaverse runtime. This includes access to crypto minting, the world scene, camera, physics, and more.
You can call these directly within your app without any extra requirements on your end. This is because the Runtime API is exposed to your code at runtime.
This provides a THREE.js renderer at runtime that can be used to
This provides a THREE.js camera at runtime.
|blob||The data of the file to be tokenized|
|object||You can define the |
|number||The id of the newly minted token|
This is a map of relative file URL -> file load URL you can
No matter how you are loading the package, whether it is an XRPK or a URL or an NFT, this map should let you access all of the app's files.
Note: Files in this map are prefixed with
This is an event that gets emitted when the app instance is deleted. You should clean up anything you app is doing here, such as removing physics, objects, timers, etc.
app.object will be automatically removed from the scene so there is no need to clean up that.
This is a function to run alongside anything you want to run before rendering.
Note: If you do mirror rendering, it should occur between
onAfterRender to ensure proper recursion.
This is a function to run alongisde anyhting you want to run after rendering.
app.object is a THREE.js object where you should attach your app (using
app.object.add, see below), this should be used instead of a
|number or URL|