NOTICE: Territory War and Battle Overlap [MEGA]
December 12, 2017 11:05PM
edited December 2017
CG_Kozispoon wrote: »Hiya Holotable Heroes,
We've received reports that confirm there is a schedule overlap between Territory Battles and Territory Wars.We'll be pushing a Hotfix that should address the following:
- Delay the start of Territory Wars by 1 hour
- This should affect this current Territory War as well as the upcoming War on the Event Calendar
- This should not affect any players who have already opted into the current Territory War
This will require a client restart of your device, and we apologize for any inconvenience this may cause. We should have this Hotfix pushed by today. We hope this notice allows our Holotable Heroes to plan accordingly.
We will be revisiting the TB and TW schedule based on sentiment around the frequency. The schedule is remaining as is throughout the holidays so players can maximize their rewards, however expect more info in the new year as we determine the best balance.
Post edited by TyloRen on
0
- 61.6K General Discussion
- -35 Developer Q&A Archive
- 2.6K New Players
- 30.7K Arena and Character Strategy
- 3.2K Individual Events
- 5.5K Guild Events
- 4.7K PVP and Rivalry
- 51K Guild Recruitment
- 751 Art and Media
- 4.2K Off Topic
Howdy, Stranger!
Replies
@CG_Kozispoon @CG_Dan @CG_Conduit23 @CG_RyDiggs @CG_JohnSalera
Territory wars player lock happens at same time at TB ends. My guild as well as others will be losing a player after this TB but we cant replace him before TW. so we will be at 49/50 but then wer cant bring someone cause they will want to be in TW. This is very impactful to guilds. We were also told there would be time in between events..... Can someone please look into and change prior to this TW?
Yeah, a one-time screw up is *way* better than a continual screw up.
I hope this is the case because these “events” are time consuming and the guilds are feeling it. It just seems as if there’s a lack of foresight. Even if it’s just one time why do it this way at all?
@Klocko @Witzkers It can impact guilds greatly. One of my friends guilds is at 120mil GP just above he has 2 people quitting and has their backfill but nothing you can do so he will lock under 120 which is now a diff prize/reward tier
WAI - they want you to farm/buy more mods, not simply move around your best ones.
In game guild: TNR Uprising
I beat the REAL T7 Yoda (not the nerfed one) and did so before mods were there to help
*This space left intentionally blank*
I do realize that for all subsequent TW there is supposed to be a 24hour wait before it starts but still, TB lasts 6 days, that's 144 hours! And then you get a 24 hour break and then the next 2 days or 48 hours is TW, then I'm assuming we get a 24hour break before TB comes again. See what I'm getting at here? Guilds will only have a 24 hour window twice every week to move members, which is outright ridiculous.
Now I understand why you can't switch out members during a TW, but why not during a TB? It's not like you can abuse the system to get more rewards, all TBs end at the same time. This way if someone wants to move to another guild during a TB they can just do so and the guild leaders can find someone else to fill in their spot. Sure it does mean that someone without a guild could always just find a guild to join right before TB ends so they get rewards, but any of the guilds getting a decent amount of stars will be invite only or already full. You'd still miss out on any of the special mission rewards that happened in a previous phase.
You could also lock the person from doing anything in TB for the phase they joined in so that you don't abuse it to get more than 50 people's contributions.
Yes, the effect could be different, but the rules governing the situation are the same. You can look at it as a penalty for guilds who lose members, or a reward for guilds and players who maintain stability. Also, we don’t even know how the matchmaking is going to work yet.
Just make sure that the player who is leaving doesn't join TW. It matches by GP, not # of guild members. The person getting the shaft the most will be the player joining you, who will have to miss out on this TW.
Suffer TW 47/50. Remember, it matches by Guild GP, not number of members.
+1 - and here's a thought - use the extra day to make sure it's bug free. I know...cray-cray.
In game guild: TNR Uprising
I beat the REAL T7 Yoda (not the nerfed one) and did so before mods were there to help
*This space left intentionally blank*
Accepting it as a 1 time issue isn’t good enough IMO. It’s easily fixable. Announce a TW delay right now by even just a few hours. As is you are forcing a small group of people to either a) miss TB rewards b) miss TW altogether or c) stick in a guild they don’t want to be in. This doesn’t impact me, but I would be ticked if I was someone it did.
THIS! ABSOLUTELY! +1!
Someone brought up the issue of removing players from a guild right after TB and not having time to replace a player for TW. This results in putting the guild at a disadvantage for the war.
Unfortunately everyone in the comments, including the original poster seemed to be worried for the guilds but not many people were worried about the individual player!
I'm not selfish but honestly this is scaring me so much as if I were removed right after TB we won't have enough time to look for a guild for TW. Given that both of these events are incredibly important for rewards, especially TB which rewards the incredibly useful and hard to aquire zetas!
I don't know if I could psychologically deal with the mental part of losing zetas. It's incredibly difficult for competitive players like me to deal with the psychological impact of missing rewards that everyone else got, including zetas...
My proposition is to allow players to participate to events like TB even after they have joined a new guild while TB is undergoing, as it is impossible to be exploited for rewards. When it comes to TW the rewards are even more crucial as zetas are so hard to get and so important. We need to ensure that a player never misses these kinds of rewards cause the disappointment and frustration might be too overwhelming to deal with!