02-25-2014, 09:25 AM
Working with ZBS is a bit cumbersome due to the fact that our plugins can span over multiple files, the studio has hard time dealing with that. For example the project analysis only works on a single file, not on the entire "plugin" (in the MCS sense).
As for the interpreter, I don't quite follow what all those functions get for parameters and what they are expected to do and what to return.
The API part will be difficult, too, since some of our API functions are overloaded - they support multiple different sets of parameters, although technically they are all under the same function name. Take for example the constructors for cBoundingBox class ( http://mc-server.xoft.cz/LuaAPI/cBoundingBox.html ) - there are four of them. I haven't seen anything in the ZBS API specs that would allow this.
As for the interpreter, I don't quite follow what all those functions get for parameters and what they are expected to do and what to return.
The API part will be difficult, too, since some of our API functions are overloaded - they support multiple different sets of parameters, although technically they are all under the same function name. Take for example the constructors for cBoundingBox class ( http://mc-server.xoft.cz/LuaAPI/cBoundingBox.html ) - there are four of them. I haven't seen anything in the ZBS API specs that would allow this.