MineQuest

Yeah, well, BukkitDev is taking a long time to review it. I assume with some of the new features, that might take some inspection. (Especially Javascript...)

Milestone 2 has been sent for approval.

Progress is moving slow due not only to exams, but also my involvement with the OpenMandriva Association.

But ignoring that, Milestone 2 is essentially complete, save for good Javascript support.

The testing that's been done by users has been extraordinary, and I really thank you guys for it. I know it seems like I'm not active at times, but your usage has really been helping me push on with it, in light of my other duties.

So, what's left? Well, if you're not using Javascript, Milestone 2 is done for you. PM me if you want a link to said Milestone 2. If you want to try the Javascript functionalities, I still have to implement events and utilities, as well as pausing and other functions. I'll get back to you on that.

But soon, Milestone 2 will make its way into the spotlight.

So I've been working on Milestone 2, and aside from the preliminary Javascript support, I'm now adding support for Targets back to MineQuest (like Targeted Events). However, the format is most likely going to be different, I think:

Instead of I'm planning to have explicit . I'm wondering if anyone has any objections to this change in syntax.

Additionally, there have been major deficiencies in our Quest Helper for some time, reflecting old versions. It's been on my todo list for a while now to provide a Quest Helper that can read documentation and available events from a list of JAR files, but I haven't gotten to it yet. If anyone would like to help contribute to such a task, please tell me!

Anyway, that's about all for now. I'll let you know more as I go on about more.

If you're experiencing bugs like this one, see the thread for a...

I've been taking a look at the Lua and Javascript runtimes for Java (LuaJ and Rhino, respectively), and since Lua and Javascript are neck-in-neck in the polls, I took the liberty of being the tiebreaker and choosing Javascript for now.

My reasons are twofold:

• Javascript is rapidly becoming popular, although Lua is also becoming popular due to its usage within ComputerCraft.

• LuaJ does not currently provide any solid solution to terminate any bad scripts (well, it does, but it involves me having to hack into LuaJ with Lua's debug.sethook, something I'd like to avoid for now). Rhino doesn't either, technically, but it's a lot easier to hook into the debugger of Rhino than LuaJ.

If anyone has any tips for LuaJ implementation, let me know and I'll see what I can do. Otherwise, Javascript it is!