Realcraft:Features: Difference between revisions
Jump to navigation
Jump to search
imported>Jailout2000 Created page with "{| width="30%" align="right" cellpadding="20" |- | {{RealcraftMenu}} |} == Implemented == These features are currently implemented in Realcraft. * Cross-platform support * MySQ..." |
imported>Jailout2000 |
||
| Line 21: | Line 21: | ||
** Player whitelist and blacklist support | ** Player whitelist and blacklist support | ||
** Server logging | ** Server logging | ||
*** Access logs for chests | |||
*** Entry logs for areas, some moderation so they cannot spam the logs by leaving/entering the area repeatedly in a small period | |||
*** Chat and command history | |||
*** Attempted access for blocked chests (i.e. chest owner X banned Y player, Y player tries to access chest) | |||
** Chest/door/area protection ''(MySQL tables are in-place for such features)'' | ** Chest/door/area protection ''(MySQL tables are in-place for such features)'' | ||
Revision as of 12:05, 8 January 2012
|
Implemented
These features are currently implemented in Realcraft.
- Cross-platform support
- MySQL database support (partial completion, see planned features)
- Player ranks
- Server and world-specific options
- Player position saving/loading
Planned
These features have yet to be implemented into Realcraft, but are planned for the future.
- Use libnoise for world generation
- Player authentication using Minecraft.net
- MySQL database support (partial completion, see implemented features)
- Player whitelist and blacklist support
- Server logging
- Access logs for chests
- Entry logs for areas, some moderation so they cannot spam the logs by leaving/entering the area repeatedly in a small period
- Chat and command history
- Attempted access for blocked chests (i.e. chest owner X banned Y player, Y player tries to access chest)
- Chest/door/area protection (MySQL tables are in-place for such features)