Blizzard announces 2nd connected realm pairing.
Posted: Wed Oct 09, 2013 3:03 pm
Blizzard has found that doing connected realms isn't as easy as they had implied in their initial announcements so they are proceeding with due deliberation.
And I'm doing the same... but I want to let you know my thoughts on where we are going.
The addon, as is, can handle any combination of member realms and report that info to WarcraftRealms.com without problem. The problems we still currently have with the addon is the in game display of results.
I want the ability to display the following combinations of results:
1: the display of all characters seen in the connected realm with the ability to break out the display based on Race, Class and Level (but not guild as that is member realm specific)
2: the display of any member realms specific data as we have seen in previous CensusPlus version. With the understanding that:
.... a: Only Guilds associated with the selected realm will be presented
.... b: Selecting a Guild as a display limiter will show all members we have seen of the guild no matter which member realm they actually log in on.
To make this happen, the member realms displayed in the connected realms list (in CensusPlus window) will be selectable button areas (using the same process we have used for selecting guilds.)
{I will probably make the logged on realm field a button also and remove the redundant display of that realm name}
Since Blizzard still doesn't know exactly how they are going to connect realms, they haven't yet been able to tell the player base. Balgair has expressed to me the concern that they might combine all the LOW pop realms into a single realm. If so that would make things extremely difficult for me to display all the realm names and use those names as triggers for individual member realm display. I'm working on the believe that Blizzard won't do that, but instead combine no more then 2 - 4 realms as a connected realm. Both of the connected sets they have announced/implemented have been MEDIUM pop realm during the mid-day time frame. We know that Blizzard doesn't want to create a multi-headed monster by creating a connected realm that goes into Queue mode every evening (when most people have the time to log in and play the game.) Queuing when special event happen like patch release is one thing, but being told you can't get connected to the game unless you wait X number of minutes every time you get on... will drive the players away.
That X number is a very tricky thing... low enough and you say "no big deal I'll go get drinks and munchies and other stuff." Too high and is it "Queued again! I'm not wasting my time waiting for this stupid game" (Instead you waste your time playing some other stupid game
)
I have run into a few more issues with the new requirement to think outside the single realm box.. since Rollie had never envisioned that his code might need to handle that situation.
Programming like life is full of compromises (too bad the politicians refuse to learn that lesson), and here a few I'm trying to work around.
The more code I add to the addon the more complex it gets and the slower it runs. I'm trying to keep some of the optimizations that Rollie had in place but the change in requirements may require less optimal code.
Since we don't know which realms will be combined into connected realms and Blizzard hasn't provided any programmer functions to acquire that information on logging into any realm, I'm have to choose one of two different paths.
A: Assume we can't know anything before we do a /census take or
B: build and maintain a list of realm memberships that can without warning be made invalid requiring either CensusPlus patching or potentially drastic action by the addon (database purges for example.)
Since B: will potentially require lots of updates and possibly changes here at the website, I'm going with option A: But that leads to a problem that we can't display the data I want to display until a /census take is triggered and the current realm memberships are learned. This usually happens within the first few /who polls.
For dedicated CensusPlus users this won't be a problem because they almost certainly have Auto-Census turned on and have set the /census timer {Minutes} below the trigger point. When these setting have been made you are already running a census snapshot before the WoW client releases control to the player.
If you don't have Auto-Census enabled or haven't set the timer below the default 30 minute interval {needs to go below 25 minutes to auto trigger census at log in, and can't be set below 5 minutes which is the minimum allowed} upon opening the main CensusPlus window you will find only incomplete data, which won't be very useful.
{Remember- /Census Timer {minutes} is used as a delay until the start of the next census snapshot when in Auto-Census mode. The delay is there for two reasons, doing continuous census runs on low pop realm is pretty much a waste of time and doing massive spamming of the /who resources irritates Blizzard. We don't want to get into the position that Blizzard decides to fix their server issues by banning CensusPlus. They have already made changes to the /who process to more closely match how they handle chat channel overloading.
To finish this wall of text... I've already had three or four variations of code changes that haven't been exactly what I want to release. I know that I will have something that will be good to go before Blizzard is ready to fully implement connected realms, but I won't be releasing any of these code changes until I am more confident that Blizzard doesn't throw us another curve ball and invalidating my changes.
A sad side note is that I fixed (again) the PAUSE button in CensusPlus, but I don't think I can release that fix until the rest of the program is ready for light of day.
And I'm doing the same... but I want to let you know my thoughts on where we are going.
The addon, as is, can handle any combination of member realms and report that info to WarcraftRealms.com without problem. The problems we still currently have with the addon is the in game display of results.
I want the ability to display the following combinations of results:
1: the display of all characters seen in the connected realm with the ability to break out the display based on Race, Class and Level (but not guild as that is member realm specific)
2: the display of any member realms specific data as we have seen in previous CensusPlus version. With the understanding that:
.... a: Only Guilds associated with the selected realm will be presented
.... b: Selecting a Guild as a display limiter will show all members we have seen of the guild no matter which member realm they actually log in on.
To make this happen, the member realms displayed in the connected realms list (in CensusPlus window) will be selectable button areas (using the same process we have used for selecting guilds.)
{I will probably make the logged on realm field a button also and remove the redundant display of that realm name}
Since Blizzard still doesn't know exactly how they are going to connect realms, they haven't yet been able to tell the player base. Balgair has expressed to me the concern that they might combine all the LOW pop realms into a single realm. If so that would make things extremely difficult for me to display all the realm names and use those names as triggers for individual member realm display. I'm working on the believe that Blizzard won't do that, but instead combine no more then 2 - 4 realms as a connected realm. Both of the connected sets they have announced/implemented have been MEDIUM pop realm during the mid-day time frame. We know that Blizzard doesn't want to create a multi-headed monster by creating a connected realm that goes into Queue mode every evening (when most people have the time to log in and play the game.) Queuing when special event happen like patch release is one thing, but being told you can't get connected to the game unless you wait X number of minutes every time you get on... will drive the players away.
That X number is a very tricky thing... low enough and you say "no big deal I'll go get drinks and munchies and other stuff." Too high and is it "Queued again! I'm not wasting my time waiting for this stupid game" (Instead you waste your time playing some other stupid game


I have run into a few more issues with the new requirement to think outside the single realm box.. since Rollie had never envisioned that his code might need to handle that situation.
Programming like life is full of compromises (too bad the politicians refuse to learn that lesson), and here a few I'm trying to work around.
The more code I add to the addon the more complex it gets and the slower it runs. I'm trying to keep some of the optimizations that Rollie had in place but the change in requirements may require less optimal code.
Since we don't know which realms will be combined into connected realms and Blizzard hasn't provided any programmer functions to acquire that information on logging into any realm, I'm have to choose one of two different paths.
A: Assume we can't know anything before we do a /census take or
B: build and maintain a list of realm memberships that can without warning be made invalid requiring either CensusPlus patching or potentially drastic action by the addon (database purges for example.)
Since B: will potentially require lots of updates and possibly changes here at the website, I'm going with option A: But that leads to a problem that we can't display the data I want to display until a /census take is triggered and the current realm memberships are learned. This usually happens within the first few /who polls.
For dedicated CensusPlus users this won't be a problem because they almost certainly have Auto-Census turned on and have set the /census timer {Minutes} below the trigger point. When these setting have been made you are already running a census snapshot before the WoW client releases control to the player.
If you don't have Auto-Census enabled or haven't set the timer below the default 30 minute interval {needs to go below 25 minutes to auto trigger census at log in, and can't be set below 5 minutes which is the minimum allowed} upon opening the main CensusPlus window you will find only incomplete data, which won't be very useful.
{Remember- /Census Timer {minutes} is used as a delay until the start of the next census snapshot when in Auto-Census mode. The delay is there for two reasons, doing continuous census runs on low pop realm is pretty much a waste of time and doing massive spamming of the /who resources irritates Blizzard. We don't want to get into the position that Blizzard decides to fix their server issues by banning CensusPlus. They have already made changes to the /who process to more closely match how they handle chat channel overloading.
To finish this wall of text... I've already had three or four variations of code changes that haven't been exactly what I want to release. I know that I will have something that will be good to go before Blizzard is ready to fully implement connected realms, but I won't be releasing any of these code changes until I am more confident that Blizzard doesn't throw us another curve ball and invalidating my changes.
A sad side note is that I fixed (again) the PAUSE button in CensusPlus, but I don't think I can release that fix until the rest of the program is ready for light of day.