Quote:

---

Rule # 1. By default, entities created with ent_create have their actions or functions run on the Server.

Rule # 2. Everything else by default runs on the same computer as the function that called it is running on.

Rule # 3. There are ways of getting around rules 1 and 2.

...

Any function called from main() will run on both the client(s) and the server. Since main runs on both, all functions called from main also run on the client(s) and the server.

---

  main() {
if (connection == 1) {
     server_only_function();  // -sv only  
}

if (connection == 2) {
     client_only_function(); // -cl only
     }

if (connection == 3) {
     server_client_function();  // -sv AND -cl
     }
}
Or even cooler still:

if (connection & 1) {
                 any_client_function();  // (-cl) or (-sv AND -cl)
}

 

/*******************************************************************************************************	
	
	Design Concept:
	
	This concept is rather simple. I'm going to change the rotation and movement to be handled on the
	client side. The servers job will then be to simply 'echo' each clients movements to all the other clients.
	
	Traditionally 3dgs expects this to be handled on the server. To prevent the server from
	sending it's automatic updates, I am setting nosend_angles and nosend_origin flags on all entities.
	
	As we gather_input from the client keyboards, each client will apply the keyforces to it's own entity. Then
	each client will send the movement coordinates of the entity via skills to the server. 
	
	The server will take these coordinates coming in from the clients and 'move' the corresponding entity. Then
	the server will 'echo' these movements to all the other clients via other skills.
	
	And finally a "client_move" function will use these 'echo' skills to move the 'echo entities' of other clients. 
	To smooth the movement effect client_move will use vec_lerp to interpolate the current position and rotation 
	of the clients' entities with these	'echoed' position updates coming from the server.  Simple huh!
	
	
	Note: This is not a prediction algorithm. Under very high latency this code will break down.
	
**********************************************************************************************************/