Originally posted by OverRated_AU
View Post
Like:
Client: Please mighty server spawn me a projectile.
Server: Ok you got enough ammo ... or no way you are out of ammo bad client.
Client: Please mighty server open me that container.
Server: Ok you are close enough ... or no way you are too far away bad client.
So far it's implemented in the Action RPG... at least regarding the container.
However I'm in doubt that the Server even is even created for the other way around that sets the server in the position to ask with some please.
Server: But please tell me when I have to despawn that projectile. Ok?
Server: And please even tell me when I have to close that container if you move.
Client: Smiles. I swear by the flowerpot of my grandma that I would tell you if it's the time for you todo so.
You could follow me? I don't think that the close event could work that way if it's a Server event ... ever. So there is nothing that prevents the client to use the Container if he chooses to cheat and just says: Shame on you server if you don't know yourself where I am if I tinker with your container then you deserve it that I still loot it from somewhere else.
Edit: Or in other words. Its the job of the client to call a server event and the job of the server to do something or reject something in the response to the request (triggered on the client) afterwards. But as far my understanding of the eventype Server goes is that it's not the job of the Server to tell the client if he should call this or not (or if this is ever verified if its a event-type that's created for the Clients wishes). Its like the server could tell me if I have to push a mouse button for a further projectile... just not manually via mouse but in hope the code in the client is unmodified (and a ServerCloseContainer comes because the Client sends it). The event that protects the container should not be an eventtype thats created to be triggered from the client but that's called from the server no matter what (if the client ever sends something to the server or not). The event might stay but only for cosmetic stuff ... like: Hey server let me know when I should close that window ... as you would refuse to let me do something with it any longer. The point is... the server does not refuses it ... if the client don't brings him to that idea. At least as far my understanding of that used Eventtype goes.
Comment