-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should create Players and Player object #36
Comments
*between client and server |
Also we can take into account entity-component-system pattern. It's commonly used pattern in gamedev but I'm not sure if it won't be overkill little tutorial/demonstration |
I think that when we start playing with oop it would be nicer if we would write classes with es6 (babel or typescript or whichever compiler which can compile down to es5). OOP code in es6 looks much clearer than es5 |
I like this ECS system. I'll take a closer look at it. |
I agree. We should write classes with ES6 :D |
But for es6 we need compiler which is impying build system. Which one you prefere? I'm suggesting gulp |
Yes, Gulp is much easier to use. I think. |
@huytd i can setup gulp with babel also I'll create issue for this |
👍 |
Should create Players and Player object.
Players should be initialized once to hold all players object. It should also have all the methods related to findPlayer, getPlayersList etc.
The Player object should have the x, y etc. And it should probably inherit the playerConfig. This object should be initialized in socket.on("welcome", function(us
Perhaps it also should be packed in webpack, so the code could be shared on the client and server side?
Thoughts?
The text was updated successfully, but these errors were encountered: