Map Scripting API _ WorkAdventure Documentation
Map Scripting API _ WorkAdventure Documentation
Do you want to add a bit of intelligence to your map? Scripts allow you to create maps with special features. Available features in the client API
Events
Camera
Create FTUE (First Time User Experience) scenarios where a first-time user will be displayed a notification popup.
Chat Create NPC (non playing characters) and interact with those characters using the chat.
Controls Organize interactions between an iframe and your map (for instance, walking on a special zone might add a product in the cart of
an eCommerce website...)
Event
etc...
Map Editor API
Metadata Please note that scripting in WorkAdventure is at an early stage of development and that more features might be added in the future.
You can actually voice your opinion about useful features by adding an issue on GitHub.
Navigation
Player
CAUTION
Players Beware: Scripts are executed in the browser of the current user only. Generally speaking, scripts cannot be used to trigger a
Room change that will be displayed on other users screen.
Sound
Start
Scripting language
State
UI Client-side scripting is done in Javascript (or any language that transpile to Javascript like Typescript).
Deprecated Functions There are 2 ways you can use the scripting language:
Extended utility functions
In the map: By directly referring a Javascript file inside your map, in the script property of your map.
Scripting Internals
In an iFrame: By placing your Javascript script into an iFrame, your script can communicate with the WorkAdventure game
Using Typescript
In Tiled, in order to access your map properties, you can click on "Map > Map properties".
Create a script property (a "string"), and put the URL of your script.
You can put relative URLs. If your script file is next to your map, you can simply write the name of the script file here.
script.js
The WA objects contains a number of useful methods enabling you to interact with the WorkAdventure game. For instance,
WA.chat.sendChatMessage opens the chat and adds a message in it.
The message should be displayed in the chat history as soon as you enter the room.
CAUTION
Internally, scripts are running inside a sandboxed iframe. Furthermore, the script itself is loaded as module with <script src=""
type="module"> . Scripts loaded as module must enforce CORS. But the iframe itself does not have any origin, because it is
sandboxed. As a result, for the script to be loaded correctly, you will need to allow ALL origins using this header:
Access-Control-Allow-Origin: *
or alternatively:
Access-Control-Allow-Origin: null
Because the script is sandboxed, a number of restrictions apply. If you want a discussion on how to overcome them, check out the
"scripting internals" documentation.
This is done to improve security. In order to be able to execute a script that communicates with WorkAdventure inside an iFrame, you
have to explicitly allow the iFrame to use the "iFrame API".
In order to allow communication with WorkAdventure, you need to add an additional property: openWebsiteAllowApi . This property
must be boolean and you must set it to "true".
In your iFrame HTML page, you now need to import the WorkAdventure client API Javascript library. This library contains the WA object
that you can use to communicate with WorkAdventure.
iframe.html
<!doctype html>
<html lang="en">
<head>
<script src="https://play.workadventu.re/iframe_api.js"></script>
</head>
<body>
</body>
</html>
You can now start by testing this with a simple message sent to the chat.
iframe.html
...
<script>
WA.chat.sendChatMessage('Hello world', 'Mr Robot');
</script>
...
Let's now review the complete list of methods available in this WA object.
Using Typescript
View the dedicated page about using Typescript with the scripting API.
Previous Next
« Inbound API Variables »