HackerTube 中文?

Overwatch Gameplay Architecture and Netcode

GDC Festival of GamingYouTube ↗

Further reading 1

Does splitting code actually split its dependencies? →Start with a rule that sends an email. Separate deciding from doing, then inspect layers, objects and abstractions: which parts must still change together when the rule changes?This video helps answer · Where do side effects belong?

Caption notes

Overwatch stores state in components and behavior in systems. Fixed steps, buffered input and replay let clients predict motion and reconcile it with the server.

Original passages · 6
components store a game state and have no behaviors systems have behaviors in store no game state
Overwatch Gameplay Architecture and Netcode · ▶ 1:56–2:06
the big side effects are invoked entirely from one call site every single frame
Overwatch Gameplay Architecture and Netcode · ▶ 21:05–21:11
we're going to replay all of your inputs to catch back up
Overwatch Gameplay Architecture and Netcode · ▶ 28:12–28:21
keep that subsystem intact they then create like a proxy component
Overwatch Gameplay Architecture and Netcode · ▶ 46:58–47:05
all major behavioral side effects are localized to that call side
Overwatch Gameplay Architecture and Netcode · ▶ 18:20–18:26
replay all of your inputs to catch back up
Overwatch Gameplay Architecture and Netcode · ▶ 28:14–28:21

Hacker News comments

View original on HN ↗