is your player object the same as your character object? learn why you should be separating them, and how to implement it in your #gamemaker projects. in fact, this technique can be used for any #gamedev project

watch on youtube:

This is telling me I desperately need to start learning how to use structs and non global scope functions 😂

I think I write pretty much all of my code just inside of object methods now. It’s life changing lol

I watched this whole video and still don't understand it. I'm going to give it a careful and slow listen then get back with questions. Looks great work as always!

Very solid idea for networked games too as it's a good "avatar" for players (literally) to ask the server to do things without having ownership of server objects, like how a player at a board-game would ask the person in control of the board-game to move the pieces.

very true. I should've talked about multiplayer some more in this video. even for local multiplayer, another cool feature is being able to have your characters go from being NPC controlled to human controlled the second a gamepad is plugged-in/removed without restarting the game

Makes me grateful that Roblox got it right first try.

Bookmarked to watch after work 👍

This is nice . SEparating responsibilities is a good practice.

Thank you for this amazing video! I really need to find the courage to do this for once!