HAHA! They admitted if geofiltering would help region selecting for others theyd accept the job done for them and be happy. Cant make up such laziness, its unbelievable.
Players were punished because they weren’t fixing it. They were making it worse for everyone but themselves. But as I’ve been told, that’s still an issue with the matchmaking, because in other games geofiltering would stop you from matching with people in other regions. In Infinite it doesn’t impact the matchmaking at all. What they probably should have done with this update is make it so you’d only connect locally if you used a geofilter. That way you could use it wouldn’t impacting anyone negatively. But I guess that’d be too hard for them?
Hey, I just realized your name is a tautology. That’s cool!
With double the player, doesn’t make sense why it would be only 30 for BTB.
I remember a few years ago with one of the COD betas, the beta servers were either 60-64 then the game released and went to 30-32. People were complaining and they openly came out and explained it was the tick rate change and said it was due to cost.
Nice name
Games like Apex Legends are on 20hz servers. April of last year, Apex had to do a blog post similar to 343’s:
https://www.ea.com/games/apex-legends/news/servers-netcode-developer-deep-dive
Yeah as much as I like Apex and a lot of ideas it brought to the table, good/stable and reliable servers were never its strong suit.
Collision does exist for enemies but not in the way that it has in previous Halos. It uses soft collision, it’s almost similar to how racing games handle hitting a light post, in those games, you kind of hit them and glide off of them to avoid you coming to an immediate stop and ruin your experience.
This doesn’t work well in a game like Halo. There’s like, initial collision but for some reason they felt the need to make the collision, “forgiving,” if that makes any sense. It’s like it you continuously push against another Spartans body, the collision gives in and allows you to phase through them.
I wish I knew why in the hell they did this. Only thing that I can even think of is that it might have to do with the fact that they removed friendly fire from social modes. In previous Halos, if a teammate wanted to troll, they could body block a doorway and you couldn’t pass through if they kept up with the input (if I remember correctly, you could kind of push teammates around slowly if they were afk).
With friendly fire enabled, you had a way to combat body blocking by damaging or killing someone who was trolling that way, in Infinite, there’s no way to combat it if they turned on team collisions.
However, that still doesn’t explain the extremely soft collision of enemy Spartans.
It’s never been officially stated but some say no collision was introduced so the bots didn’t get in each others or players way.
If that’s the case I would rather have no bots. Yet another unnecessary problem created by 343.
༼ づ ಠ_ಠ ༽づ Summon Collision
I’ve definitely had instances where me and an enemy walk through each other in a narrow doorway. The alert sound goes off and we both do a 360!
Also if it was they could always turn it on for ranked. I’m guessing.