🎮 UE4 Replication – Part 2: Game Instances – Unreal Engine

35
9



🎮 Unreal Engine Replication Series – Part 2: Game Instances

In part 2 of our replication tutorial series, we are introduced to the idea of game instances – not to be confused with the “Game Instance” class that’s built in Unreal but the idea of multiple instances of the game running on different machines (clients vs. server). We use the practical example of sprinting to really help us understand some fundamental multiplayer concepts when it comes to replication and communication between game instances.

➖ ➖ ➖ ➖ ➖ ❗ Watch Next ❗ ➖ ➖ ➖ ➖ ➖
⏪ Part 1: What is Replication? –
⏩ Part 3: Network Relevancy –
⏩ Part 4: Multicast & RepNotify –

➖ ➖ ➖ ➖ ➖ 💙 Reach Out 💜 ➖ ➖ ➖ ➖ ➖
I ❤️ hearing from you guys so please don’t be shy! Let me know what you’d like to see in future videos.

📣 If you find yourself stuck, speak up! There’s a lot of awesome developers here that are willing to help!

👍 If you found this video helpful, do yourself a favor by doing me a favor and hitting that juicy red subscribe button! 💚

👀 Thanks for watching

➖ ➖ ➖ ➖ ➖ 🙋‍♂️ Contact Info 🤙➖ ➖ ➖ ➖ ➖
💬 Discord: bry#7777
🎤 Discord Server:

➖ ➖ ➖ ➖ ➖ 🔻 Copyright 🔻 ➖ ➖ ➖ ➖ ➖
Portions of the materials used are trademarks and/or copyrighted works of Epic Games, Inc. All rights reserved by Epic. This material is not official and is not endorsed by Epic.

Nguồn: https://alimentproteine.com/

Xem thêm bài viết khác: https://alimentproteine.com/game/

35 COMMENTS

  1. Phenomenal, but I think just for your own sanity you could have less animations. But the presentation made it really easy to understand the concepts!

  2. You know what? I think I know what I feel by watching your videos… I feel like I was being teached by Rick Sanchez…

  3. It’s still not safe the way you’re doing it as you are assuming “run on server” (the authority) is always “a server / not a player” while this is not true. You should always do a #1 is-server node check (bool) or #2 has authority node even before letting the authoritative “server / owner” change a value. Other than that nice tutorial.

  4. Your tutorials are very helpful and visuals are absolutely great what a brilliant way of teaching. Thank you so much.

  5. It seems to be quite troublesome where we always need to duplicate the code twice for client side and RPC. Is there any ways to simplify this process?

  6. if it's so freaking easy to ban anyone one who speed hacks, WHY DONT PUBG BAN HACKERS INSTANTLY? It's so annoying.

  7. Please NEVER stop making those videos, they are more informative than 99.99% of all videos about UE4 replication on the net, and are comedy gold too 😀

    PS: those graphs are gold, they make it rly easy to understand stuff

  8. this was amazing, even the tip of verifying information that the client sends was fucking amazing! holy shit keep it up man, i'm no beginner, i would say i'm above-beginner (slightly) and this helped me out tremendously for thinking ahead for not trusting clients, i didn't know of such a great way to stave off hackers xD i sense a lot of bans in my games future xD

  9. 6:30 – 7:10 in this tutorial would have saved me 100 hours of figuring out replication issues if I understood the concept from the beginning.

  10. Thank you so much for this. You have the best tutorials on YouTube… even though you only have like two, I can't wait for the rest

  11. First video was great, but this one blew my mind!!!!! Never seen an easier explanation about server and client side interactions. Well worth the wait, keep up the good work. I can't wait for the next video in 2035!!!!!!!!!!!

  12. This is great, I really like how you explain things and it makes it very visually understandable for a more Visual person like me when you use the images/graphs. Well done, can't wait for the next installment.

  13. It was good. Unfortunately I liked the visual demonstration and I think it did a good job showing the actor replication part. I think that it could have been brought up again to show the variables being updated when the RPC is called to demonstrate how variables are passed to the server. A lot of people new to replication will try to update their server side variable inside the RPC by pulling off from a variable node instead of passing it through the RPC. You did mention the process, but visuals would be great. Food for thought for Multicasting maybe 🙂 Looking forward to it.

LEAVE A REPLY

Please enter your comment!
Please enter your name here