CoreScript: Difference between revisions
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
The first appreances of Corescripts in the client were in 2011. Originally, they were streamed into the client by asset files, which were [[Signatures|signed]] using the <code>rbxsig</code> format. In 2014{{efn|The first known ROBLOX client version to have local corescripts was 0.167.1.51539 (dated 9/11/2014).}}, this system was changed to allow for "local corescripts" (which allowed for the corescripts to be stored locally, in the <code>content/scripts</code> folder. | The first appreances of Corescripts in the client were in 2011. Originally, they were streamed into the client by asset files, which were [[Signatures|signed]] using the <code>rbxsig</code> format. In 2014{{efn|The first known ROBLOX client version to have local corescripts was 0.167.1.51539 (dated 9/11/2014).}}, this system was changed to allow for "local corescripts" (which allowed for the corescripts to be stored locally, in the <code>content/scripts</code> folder. | ||
There are also Lua virtual machines in ROBLOX's engine. | There are also Lua virtual machines in ROBLOX's engine. In clients, there are different threads that run scripts from one identity. This ensures that user scripts are not mixed with scripts authored by ROBLOX. There are currently only two virtual machines, one for corescripts and other threads that have <code>RobloxScript</code> access and another for all the other threads. In studio builds, there is a third virtual machine used for studio plugins. | ||
Some behaviors to note with corescripts are: | Some behaviors to note with corescripts are: |
Revision as of 00:44, 18 October 2023
This page is currently a work in progress! Information on this article may be incomplete or inaccurate. |
Corescripts are essential to make clients operate and function in modern ROBLOX.
The first appreances of Corescripts in the client were in 2011. Originally, they were streamed into the client by asset files, which were signed using the rbxsig
format. In 2014[a], this system was changed to allow for "local corescripts" (which allowed for the corescripts to be stored locally, in the content/scripts
folder.
There are also Lua virtual machines in ROBLOX's engine. In clients, there are different threads that run scripts from one identity. This ensures that user scripts are not mixed with scripts authored by ROBLOX. There are currently only two virtual machines, one for corescripts and other threads that have RobloxScript
access and another for all the other threads. In studio builds, there is a third virtual machine used for studio plugins.
Some behaviors to note with corescripts are:
- The scripts have the `RobloxScript` context.
- There are other corescript signing formats besides
rbxsig
, which are noted in the signatures page. - Corescripts are executed in its own Lua virtual machine. [b]
Official corescripts can be found in the ROBLOX GitHub Repository.
References
Footnotes
- ↑ The first known ROBLOX client version to have local corescripts was 0.167.1.51539 (dated 9/11/2014).
- ↑ All scripts in ROBLOX have different security contexts.