I had 3 new ideas for features:

- PLAYERNAME_EVENT ...is called when a client changed his playername
- enet_lock(var* variable) ...locks a variable/array/string/struct
- enet_send_var() ...allows also to send variables of type double/long/int/float/char

The enet_lock() function is very important when it comes to make your game cheating secure.

Imagine the following: In an array you store the health of all players. Now a bad guy could hack a client application and use an enet_send_ function to change the array content. If you used enet_lock() and locked the array, the array can't be changed through a send function.