Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Quite frankly, I don't think I'm at liberty to divulge details, but generally, Vanguard was in concept, a multi-threaded server, where each zone (chunk) was a thread. There was lots of message passing, even if you weren't actually crossing server lines. 3/?
Which seemed stupid. If the entity you're attacking is in your zone (99.9% of the time that was the case), just handle the attack message immediately. Today, in multi-threaded games, message passing from one sub-system to another is foundational. 4/?
Lots of Vanguard was kinda "one level too low" in terms of abstraction. Serializing messages was a chore and error prone. It got better over the years, but that was well after launch. And this is only discussing the server code of the game. Nevermind other issues. 5/?
I take a lot of lessons from that codebase with me in my career. Many things multithreaded concepts were easier to understand because of my experience with it, despite being only running on basically 1 thread. 6/?
Vanguard gets a lot of crap, especially for it's spaghetti code. But really, I think the original authors of the (server) codebase saw a future few other engineers could, including myself until recently. It was ambitious and in ventured into untreaded waters.
/Thread I guess. As an afterthought, I hope I one day work on a project with similar ambitions as Vanguard. The enormous seamless world could be done at the scale Vanguard aimed for.
Want to clarify about this tweet. Maintaining the separation of subsystems via a message was a boon, just one I didn't see at the time. With the experience of working on multi-threaded game engines, this was actually the best way to go.https://twitter.com/tloch14/status/978814775785394176 …
Mostly the benefits were in regards to code clarity, and knowing where and when data would be handled.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
