Difference between revisions of "JavaScript"
From Roll20 Wiki
Andreas J. (Talk | contribs) m |
Andreas J. (Talk | contribs) m |
||
Line 1: | Line 1: | ||
{{Pro only}} | {{Pro only}} | ||
− | Users can use [https://en.wikipedia.org/wiki/JavaScript JavaScript] on Roll20 in two different cases, both of which are fairly restricted: | + | Users can use [https://en.wikipedia.org/wiki/JavaScript JavaScript] on Roll20 in two different cases, both of which are fairly restricted, and requires {{pro}} subscription to access: |
− | ::'''1.''' When editing or creating [[ | + | ::'''1.''' [[Character Sheets]]: When editing or creating [[BCS|custom character sheets]], JavaScript can be used in [[Sheetworkers|sheetworkers]] for creating more advanced backend features. |
− | + | ::::* [[Sheetworkers#JavaScript_Restrictions|Sheetworkers - JavaScript Restrictions]] | |
− | :: | + | |
+ | ::'''2.''' [[API|API Scripts]]: When editing or creating [[API|API Scripts]]. | ||
+ | ::::* The Roll20 API functions by running a special server-side virtual machine for each campaign. This provides an [[API:Sandbox_Model|API sandbox]] where your custom scripts can run without any danger of them affecting other user's campaigns. | ||
See Also: [[Javascript:Best Practices]] | See Also: [[Javascript:Best Practices]] |
Revision as of 14:26, 25 July 2021
This is about a Roll20 feature exclusive to Pro-subscribers (and often to players in a Game created by a Pro-subscriber). If you'd like to use this feature, consider upgrading your account. |
Pro
info subscription to access:
- 1. Character Sheets: When editing or creating custom character sheets, JavaScript can be used in sheetworkers for creating more advanced backend features.
- 2. API Scripts: When editing or creating API Scripts.
- The Roll20 API functions by running a special server-side virtual machine for each campaign. This provides an API sandbox where your custom scripts can run without any danger of them affecting other user's campaigns.
- 2. API Scripts: When editing or creating API Scripts.
See Also: Javascript:Best Practices