12-07-2013, 06:22 PM
Hello again.
Yes, we've moved to GitHub, about 3 months ago, and since then it seems we're gaining some momentum. A few people have joined the project, others have posted a few patches. Here's the page on github: https://github.com/mc-server/MCServer
As for the changes, I don't really remember much what it was like 9 months ago, but I suspect the world generator has evolved a bit, as usual. The fluid simulators have stopped at Floody, unfortunately, no-one has had the guts to implement vanilla-like simulator yet. However, the underlying framework has changed a lot to allow for faster code, many parts now have again direct access to chunks, but this time in a safer manner (see the cChunk::UnboundedRel... functions). It also seems we have redstone mostly working, but I haven't tested it out yet, so can't really say
One of the features that I consider quite neat is the APIDump plugin. Remember the times we updated the API in the wiki? Well, no more, there's a plugin that generates the documentation out of the actual API and a description "database". Have a look at the output here: http://mc-server.xoft.cz/LuaAPI/
On a related note, very recently we've had a breakthrough, we made it possible for MCServer to use LuaRocks. It's a vast repository of libraries for Lua programs, including database access modules, xml parsing, socket networking and many others ( http://luarocks.org/repositories/rocks/ )
We're also geared towards player XP. The base code for remembering the player XP and for XP orbs is there, enchantments are stored in cItem and available to plugins through the API. The actual enchanting is not implemented yet, though, although it should be pretty straightforward now.
As for the compatibility, we're still compatible with any release between 1.2 and 1.7.2. However, we're almost decided that once the 1.7.x protocol is mainstream and with 1.8, we'll cut off the support for 1.2 - 1.6.
There hasn't been much change in the ChunkWorx, I've just updated it once for a change in cIniFile API, didn't touch it otherwise. It still keeps working real fine (although the code is a weird mess
Yes, we've moved to GitHub, about 3 months ago, and since then it seems we're gaining some momentum. A few people have joined the project, others have posted a few patches. Here's the page on github: https://github.com/mc-server/MCServer
As for the changes, I don't really remember much what it was like 9 months ago, but I suspect the world generator has evolved a bit, as usual. The fluid simulators have stopped at Floody, unfortunately, no-one has had the guts to implement vanilla-like simulator yet. However, the underlying framework has changed a lot to allow for faster code, many parts now have again direct access to chunks, but this time in a safer manner (see the cChunk::UnboundedRel... functions). It also seems we have redstone mostly working, but I haven't tested it out yet, so can't really say
One of the features that I consider quite neat is the APIDump plugin. Remember the times we updated the API in the wiki? Well, no more, there's a plugin that generates the documentation out of the actual API and a description "database". Have a look at the output here: http://mc-server.xoft.cz/LuaAPI/
On a related note, very recently we've had a breakthrough, we made it possible for MCServer to use LuaRocks. It's a vast repository of libraries for Lua programs, including database access modules, xml parsing, socket networking and many others ( http://luarocks.org/repositories/rocks/ )
We're also geared towards player XP. The base code for remembering the player XP and for XP orbs is there, enchantments are stored in cItem and available to plugins through the API. The actual enchanting is not implemented yet, though, although it should be pretty straightforward now.
As for the compatibility, we're still compatible with any release between 1.2 and 1.7.2. However, we're almost decided that once the 1.7.x protocol is mainstream and with 1.8, we'll cut off the support for 1.2 - 1.6.
There hasn't been much change in the ChunkWorx, I've just updated it once for a change in cIniFile API, didn't touch it otherwise. It still keeps working real fine (although the code is a weird mess