WRT name placement: I tried that initially. Stuff tends to get lumped together and it actually makes it *worse*.
"Take it from me man, networking code takes 80-90% of the time in multiplayer games."
This is definitely untrue. However, I will say it will take quite a while to "upgrade" it to being multiplayer.
"Why? Because it's the most complicated part that requires you to work on 2 separate programs simultaneously."
I think the renderer is more complicated, actually. And no, the client and the server are basically the same program, so I can actually do virtual networky stuff with relative ease, without actually having to serialise the networked data. I just need to add an API for it, really.
I also need to add an API for loading maps and whatnot.
WRT accounts: Yeah, I do have plans for allowing authentication, although I will probably need to implement HTTP queries somehow. But yeah, I'm more fond of what Triplefox is suggesting, rather than what Null is suggesting.
So, the TODO:
- Implement map loading/switching/saving on the Lua side of things.
- Implement proper security for pathnames and whatnot, for reading and writing and all that crap.
- Implement an actual networking API for Lua.
- Get it all implemented on the Lua side.
- Buld cahirs and snip.