QuackShot

Thankyou Fraser 👍

When prioritising a device using the R2's traffic prioritisation feature (specifically over WAN), do I need to create a second, seperate rule for the same device to encompass WAN traffic in addition to a rule for traffic on LAN, or will a single rule with the "apply to WAN" box ticked cover both LAN and WAN prioritisation?

Not great. Peak times it's OK, but at other times of the day I find myself most likely to get put onto US servers (the R2's Geofilter shows the location) Played Three ranked matches today at 157ms, 87ms and the third at 115ms all on US servers. Shots not registering, OHK's and dying around corners. I've about done with the game at this stage, if 343i can't make the effort to add regional Server Selection as a menu option (something included in both Halo 5 and MCC) then I won't be playing their game and I'll find something more worthy of my time. Disappointing because I've invested a fair amount of time into the multiplayer, having played around 1370 matches in total (and purchased the odd skin to support the team too). Oh well, Forbidden West is on the Horizon (forgive the rubbish pun) and the week after Elden Ring, also an excuse to have a go at Hunt Showdown, a game that everybody tells me is great - so plenty to keep me busy!