I am an indie developer who is working on a number of game engines and game ideas, notably in the Java language. My primary focus is in creating an "RPG Maker" in Java, with separate editor, engine, and platform infrastructure that is extensible. These will be released as open-source projects, with as-yet-undetermined licensing that should be (somewhat) permissive, while allowing game authors using such components to assert their own additional permissions for private game content, as possible.
This post is a collection of my thoughts on scripting in a Java-based engine.
In researching ways and means of extending an application, as mentioned in my premiere post in this blog, I've mentioned that both editor and engine should be extensible. To wit, this includes creating a Service-Provider Interface of sorts, that can be used by other programmers. But, the opposite side of the coin is in scripting of several aspects of game logic.
I admit first that I'm no expert in any of this; and where I could in any way speak with authority in this regard, is where I've done a little research of what's possible. Thus far, I believe there are different aspects of scripting solutions: one is in using something built-into the JDK (like Rhino or Nashorn extensibility), or by third-party scripting solutions.
Another "complication", if you will, of scripting is in the scripting structure, and in variable and method access between application and script, and even if scripts can access other scripts. Now, I know that Lua scripts can require (depend upon) other scripts; but I don't know if that goes the other way as well, if scripts can require any specific API from the application....
No blogs were found matching the criteria specified. We suggest you try the blog list with no filter applied, to browse all available. Join now to share your own content, we welcome creators and consumers alike and look forward to your comments.