A team member mentioned a "port punchthrough"... A feature that makes sure people don't have to manually open ports when they start a server.
Would something like this be a realistic feature request?
This is only supported by some routers, so it's not worth to implement this.
I can see lyingmime's point. I am only using the variable sending feature, and the event feature, and making my own custom ent management system because i need complete control of what entities are where, on what machines.
But you can do this with the current entity management. The management only does creating the entity everywhere and gives it a unique pointer so that the entity can be controlled by every participant. After that it's up to you, the entity manager does nothing to update the positions, angles, skills or flags. => you have still pretty much room to do whatever you like.
What makes your project so unique that you can't use the entity built in entity management functions? This could help me to improve it.
I don't get the point why it's needed to permanently create/remove an entity if it get's out of this "range" like lyingmime mentioned. If you don't want that this entity is visible, use the invisible flag. And if you don't want that this entity produces traffic, don't send something to the clients that don't see the entity.
This are the new macros:
#define MY_GLOBPOINTER enet_ent_globpointer(my)
#define MY_CREATOR enet_ent_creator(enet_ent_globpointer(my))
#define MY_CLIENTID enet_get_clientid()
#define MY_CONNECTION enet_get_connection()
Are you using such macros? What else do you think would be useful?
I forgot to post a feature that I've already implemented: - enet_send_array/skills/flags produce less traffic
I edited my old post!
