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ää
I don't remember the exact hire date, but I landed my first job in the games industry 10 years ago this month, as a designer for @vanguardsoh.
My time on that project set me on course to become an engineer having touched far more disciplines than I can remember.
I haven't revisited memories from my Vanguard days in awhile, but I recalled when I introduced this bug into the game: https://www.youtube.com/watch?v=X-fbVO6ZUkg … This bug in particular taught me a lot about architecture traps to look out for in a codebase riddled with them.
For those who weren't there or it's not obvious, Vanguard's design was to allow absurd movement speeds, even during combat. Calculating run speeds was way out of control and difficult to reason about for designers.
The goal was to make it more understandable, more reliable, and let the players in on how those calculations worked as well. Content being made trivial by kiting needed to be reigned in as well.
Source of the bug was in having too much state to control run speed and it not always being clear when your runspeed needed to be recalculated, or rather it being calculated too many times while your character was in an odd state and not completely "unmounted".
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
