tayasuccess.blogg.se

1. #WOW COMPANION APP SHADOWLANDS FULL#
2. #WOW COMPANION APP SHADOWLANDS CODE#
3. #WOW COMPANION APP SHADOWLANDS PC#

Much of the code that was written to support the Battle for Azeroth expansion was written on top of the existing Legion code, which made it challenging to understand what code was actively in use. This code may seem familiar if you look at any add-ons that use the currency system in Shadowlands-that’s due to the shared-code framework that allows the WoW Companion App to share features with the main game. That means that every expansion is now able to automatically request its own currency types instead of having to manually specify which currencies we want.Īfter: Each expansion can ask for its own currencies.

#WOW COMPANION APP SHADOWLANDS PC#

Rather than continue to add more currencies to the same message for Shadowlands, we chose to port the entire currency system in the PC client to the new shared-code framework that was developed for Battle for Azeroth. In Legion, the app specifically requested your Order Hall Resources for Battle for Azeroth, we simply added War Resources to that message. The app itself also had a number of places that were extended to specifically support Battle for Azeroth. Legion follower or Battle for Azeroth follower), and the request for World Quests needed to include which zones it wanted quest data for. For example, the request for Follower data needed to be able to specify a Follower type (e.g. This time, however, we needed the ability to fetch data for any expansion selected, which meant going through all of the server functions that respond to mobile requests and changing them to accept parameters specifying which expansion to fetch data for. When the time came to switch over to Battle for Azeroth, we changed those functions to return Battle for Azeroth data instead. When the Legion Companion App was originally developed, most of the server code that handled requests from the app was purpose-built to only return Legion data. We needed to break up expansion-specific assets to minimize the app’s resource usage.We needed to split expansion-specific UI code apart to keep functionality separate.The app needed to clear out any data for your current expansion content and request data for a new expansion from the server.And while there was not a lot left to implement, it did mean we had some work to do to cleanly separate Legion and Battle for Azeroth from each other.Ĭreating the multi-expansion framework required three major pieces: In what turned out to be a bit of a mixed blessing, most of the Legion-specific code was still present in the app, and we still had the original Legion assets in our source control, which made re-adding Legion content the perfect test for our new multi-expansion framework. The Companion App will let players choose between Legion and Battle for Azeroth starting at Shadowlands pre-patch, with Shadowlands content becoming available at the launch of the expansion.

#WOW COMPANION APP SHADOWLANDS FULL#

We also knew that with the arrival of Shadowlands, players would have the option to level their alts through Legion via Timewalking Campaigns, and we wanted to make sure those players would have full mobile support for their level-up experience. We briefly discussed the option of supporting only partial functionality from previous expansions to maximize our ability to work on Shadowlands content, but we quickly decided that we wanted to restore as much functionality as possible. In addition, the mobile team was eager to give the community what they wanted and bring back Legion content. We know that players were disappointed to lose access to Legion content within the app when we made the switch, so we made a commitment with Shadowlands to support more than one expansion at a time. The tradeoff was that we weren’t able to build out the kind of framework that would be necessary to support more than one expansion at a time-so we swapped the single expansion that the app supported from Legion to the latest expansion, Battle for Azeroth. Leading up to Battle for Azeroth, we made the decision to prioritize several major back-end improvements, including the ability for the app to share code with the PC client, which allows us to take advantage of many of the features and tools that are available to the main game’s UI (user interface) that the app previously did not have access to. The Companion App was originally designed to support one expansion: Legion. We know it’s a feature many players have been asking for, and today we wanted to share some of the challenges and decisions involved in making this kind of large-scale tech change. One of the biggest technical upgrades we made to the WoW Companion App for Shadowlands is the ability to support multiple expansions.