It doesn't. When Skript parses a file, it creates several objects to represent the script and stores it in memory.
The only JVM bytecode that Skript uses is what's available in its jar (and addon jars, of course).

 

To expand upon what @Rezz said, Skript doesn't keep a parsed script together. It's broken into parts depending on the events, commands and other features it has.

 

I see, thanks for the info.

 

I recommend you read this: http://www.craftinginterpreters.com/
It's really interesting, but it's not complete yet

 

I'd be tempted to get a few people together and go through that and make a new Skript. I've made a very basic (and once working), plugin like Skript called Zetox (https://github.com/nfell2009/Zetox), but it's designed completely wrong (parses a script on every event).

 

It would be awesome if there was a project that allowed Skript addons to work on Zetox by having classes with the same methods in Skript.

 

Could do it quite easily. Just fake a load of Njols packages and classes.

 

Maybe even have a "compatibility" type config for addons, for example if an addon fails to load because it detected a class; have a config option to return false for a specific class.

 

https://docs.oracle.com/javase/8/docs/technotes/guides/scripting/prog_guide/about.html

I think this is very interesting, I'm actually going to look into this further.

--- Double Post Merged, Jan 27, 2017, Original Post Date: Jan 27, 2017 ---

More infos

http://www.javaworld.com/article/2071821/core-java/build-your-own-scripting-language-for-java.html

--- Double Post Merged, Jan 27, 2017 ---

Even more infos

http://www.drdobbs.com/jvm/jsr-223-scripting-for-the-java-platform/215801163