Oklahoman Posted March 17 Posted March 17 When you click on a character name in chat, one of the many options you get is "Invite to Team" and "Invite to League". It seems this essentially runs the command /i CharacterName and /li CharacterName respectively. I even get an error message occasionally saying /i and /li aren't valid commands - probably some weird alignment issue, but inviting again seems to work. There could be some conveniences to us team and league leaders if that were changed to /i @GlobalName and /li @GlobalName. The situations I run into where this would be helpful is when people are alting. Ideally, a player will ask if they can alt, they do so, then send you a tell (or post in broadcast, or whatever) with their alted character name so you can invite them from there. To be sure it's the same person, we sometimes use code words ("bagel") or take a few seconds to run a /getglobalname on their pre-alted character. And, sometimes we mess up and accidentally give away someone's spot. If I could just click on their pre-alted character name a few seconds after they asked to alt and invite them again (which would send to the global rather than the character name) it could save a bit of time and potentially some frustration on everyone's part. 4 Oklahoman, Okie, Vayne Glorious, Sooner Magic, Treehugging Wacko, Boy Band, etc Farming Incarnate Salvage - 1 salvage roll every 15 minutes! || Why NO TELLS to join your little MSR thing? Using DEMORECORD To Find Who Is Sabotaging Lambda Badge Runs https://www.twitch.tv/oklahomancoh || @oklahoman.bsky.social
Akisan Posted March 17 Posted March 17 1 hour ago, Oklahoman said: I even get an error message occasionally saying /i and /li aren't valid commands - probably some weird alignment issue, but inviting again seems to work. I've seen these errors as well - pretty sure they're what the game spits out when you try to invite a character that is zoning. Otherwise, yeah, this would be a nice QoL benefit!
Oklahoman Posted March 18 Author Posted March 18 19 hours ago, Akisan said: I've seen these errors as well - pretty sure they're what the game spits out when you try to invite a character that is zoning. Maybe, but I get this a lot when I form MSRs in RWZ or Hami raids in The Abyss. In both cases I don't invite from tells - I only invite from broadcast so I can be sure they are in zone. It's possible they zoned in, immediately broadcast for an invite, and I immediately invited - and the overall system hadn't "firmly planted" them in zone yet... I guess? Dunno, that explanation sounds like the time my brother was told by tech support that the reason his wi-fi was acting up was because it was windy outside and blowing the signal around. Oklahoman, Okie, Vayne Glorious, Sooner Magic, Treehugging Wacko, Boy Band, etc Farming Incarnate Salvage - 1 salvage roll every 15 minutes! || Why NO TELLS to join your little MSR thing? Using DEMORECORD To Find Who Is Sabotaging Lambda Badge Runs https://www.twitch.tv/oklahomancoh || @oklahoman.bsky.social
Akisan Posted March 18 Posted March 18 1 hour ago, Oklahoman said: Maybe, but I get this a lot when I form MSRs in RWZ or Hami raids in The Abyss. In both cases I don't invite from tells - I only invite from broadcast so I can be sure they are in zone. It's possible they zoned in, immediately broadcast for an invite, and I immediately invited - and the overall system hadn't "firmly planted" them in zone yet... I guess? Huh. I usually get weird invite errors when I'm inviting from tells, not from broadcast/local. And that alignment bit doesn't even make sense in the Abyss - isn't that one red-only? Perhaps there's a hidden cooldown on those commands to prevent spamming/botting of some kind, and you're just inviting people faster than the engine thinks you should be able to? 1 hour ago, Oklahoman said: Dunno, that explanation sounds like the time my brother was told by tech support that the reason his wi-fi was acting up was because it was windy outside and blowing the signal around. I've only ever heard of one situation where that was the real-ish reason: the wifi was extended from another building, and the high winds did not nice things to the antennas that the wifi was transmitted between buildings with.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now