This is a documentation for Board Game Arena: play board games online !

SandboxScripts: Difference between revisions

From Board Game Arena
Jump to navigation Jump to search
Line 35: Line 35:
Save & publish your project, starts a test session, click on the previous element : your message appears in the log on the right!
Save & publish your project, starts a test session, click on the previous element : your message appears in the log on the right!


= Functions you can use in your Lua Sandbox scripts=
= Functions you can use in your Sandbox scripts=


==addToBgaLog( txt )==
== Debugging functions ==
 
=== bga.trace( txt ) ===
 
Write something immediately in the BGA log (on the right of the screen).
 
This is the most practical way to debug your script :)
 
Note : you can also pass an object in parameter. This will dump the content of this object in the log.
 
=== bga.exit( txt ) ===
 
Stop the script immediately, display the "txt" messages and cancel (ie : rollback) on every previous API call except bga.trace :
 
Again : ALL api call are canceled and there will be no visible changes on the interface (ex : no moves, no visible property changes, ...). Only "bga.trace" API commands are kept so you can debug.
 
bga.exit is very practical when you want to repeat a game action again and again to debug it : with a call to bga.exit at the end of your script, you make sure that your game situation will be kept unchanged after each test.
 
 
== bga.log( txt )==


Write something in the BGA log on the right.
Write something in the BGA log on the right.
Line 43: Line 62:
This is also a very practical to debug your script ;)
This is also a very practical to debug your script ;)


Note : you can also pass an object in parameter. This will dump the content of this object in the log (for debugging purpose).


==getElementById( id )===
==getElementById( id )===

Revision as of 11:34, 14 December 2016

This is the reference of functions you can call from your Sandbox scripts.

Javascript

BGA Sandbox scripts are written in Javascript.

Using Javascript, you can write scripts to automate moves for your Sandbox games & provide rules reinforcement.

Important : in the opposite of the most common usage of Javascript, Sandbox scripts are executed on server side.

BGA API

To interact with your BGA Sandbox game, we provide you an API.

With this API, you can get properties values of game elements from the current game situation, modify them and/or trigger the game actions (ex : move this element here, flip this card, and so on).

Sandbox Scripts Hello World

From Sandbox editor "interface view" tab, select an element, and access to its property (top right icon).

Go to "Scripts (advanced)" section.

In front of "When this element is clicked", enter "onMyClick".

Close the window. Go to "script view" tab.

Enter the following :

function onMyClick( element_id )
{
   bga.log("Hello world! You just clicked on element " + element_id + ". Congrats!");
}

Save & publish your project, starts a test session, click on the previous element : your message appears in the log on the right!

Functions you can use in your Sandbox scripts

Debugging functions

bga.trace( txt )

Write something immediately in the BGA log (on the right of the screen).

This is the most practical way to debug your script :)

Note : you can also pass an object in parameter. This will dump the content of this object in the log.

bga.exit( txt )

Stop the script immediately, display the "txt" messages and cancel (ie : rollback) on every previous API call except bga.trace :

Again : ALL api call are canceled and there will be no visible changes on the interface (ex : no moves, no visible property changes, ...). Only "bga.trace" API commands are kept so you can debug.

bga.exit is very practical when you want to repeat a game action again and again to debug it : with a call to bga.exit at the end of your script, you make sure that your game situation will be kept unchanged after each test.


bga.log( txt )

Write something in the BGA log on the right.

This is also a very practical to debug your script ;)


getElementById( id )=

Get an object with all the properties of the element with specified ID.

Throw an exception if the element does not exists.


getElementIdByName( name )=

Get the ID of a Sandbox element from its name.

Return null if there are no element with this name. Throw an exception if there are more than 1 element with this name.

moveElement( element_id, target_id )

Move element to specified target id.