Poll: 4 Day Cooldown Guild Rejoin Change.

[sociopathix]

So it looks like only 7 potatoes who either don't siege, or hate the people that do voted to keep this extremely random and unpopular change.

East/West/PN all seem to agree on something again. Let's not kill sieges.

Yep. While I'm inclined to agree that guilds who hold castles should keep the membership necessary to continue to hold them, it denies content for players who don't want to stay in castle-owning guilds the entire time but who still would like to participate in sieges. There are other problems with the castle system in general that could be fixed or improved without throwing on a timer bandaid that no one seems to want.

 

[Joey]

Ah, you're right. An additional if/else statement is probably beyond them to implement.

I found some tutorials in case they need help.

If/else in Lua:

If/else in C#:

If they are forced to use C++ for this (which I doubt, but it's possible), If/else in C++:

You seem like you have a wonderful personality thank you for your contribution to the discussion.

 

[Mitis]

Going to have to say no to this one. Definitely don’t like this change. @HNIC_Steamroller basically explained my thought on the whole change.

 

[lightsenshi6]

this is hardly a valid argument. everything can be worse.

I didn't say that I agreed with the change, because I don't. I simply pointed out that it could be worse, especially how guilds seem to work in this game.

 

[Frontbutt]

Lol rip first time guild join, a family member of mine is brand new to the server and joined a starter guild a few days ago. He left that guild today, thinking he could join another guild right away as it was his first guild. He got ArcheRaged and now is stuck in cooldown town for 4 days. Awesome implementation could you guys at least test this shit before tossing it into the server ?

 

[Driveby]

@Frontbutt .... so you're saying that it doesnt work , even for people who are legitimately dropping a guild and rejoining another?

 

[Frontbutt]

@Frontbutt .... so you're saying that it doesnt work , even for people who are legitimately dropping a guild and rejoining another?

Yeah it does not work.

 

[Sjinderson]

Lol rip first time guild join, a family member of mine is brand new to the server and joined a starter guild a few days ago. He left that guild today, thinking he could join another guild right away as it was his first guild. He got ArcheRaged and now is stuck in cooldown town for 4 days. Awesome implementation could you guys at least test this shit before tossing it into the server ?

Have them restart their game.

@Frontbutt .... so you're saying that it doesnt work , even for people who are legitimately dropping a guild and rejoining another?

It only applies to the first guild they ever join

 

[Frontbutt]

He tried that, and it is his first guild as I stated above. Nut uh uh not this time.....

 

[Kezz]

Have them restart their game.

@Sjinderson he did restart his game. Several times. The cooldown message also appears for the person trying to invite him. It's not a visual error. It is an error in game mechanics.

It only applies to the first guild they ever join

He was in one guild ever. Dropped that guild to join a new one today, and received the 4 day cooldown.

 

[Sparkle]

@Sjinderson he did restart his game. Several times. The cooldown message also appears for the person trying to invite him. It's not a visual error. It is an error in game mechanics.

He was in one guild ever. Dropped that guild to join a new one today, and received the 4 day cooldown.

He needs to restart the game after he dropped the guild for the timer to update for him. If it didn't update, then he didn't restart the game after he dropped the guild.

 

[Kezz]

He needs to restart the game after he dropped the guild for the timer to update for him. If it didn't update, then he didn't restart the game after he dropped the guild.

That worked. Character selection screen did not work. Thank you.

 

[Kezz]

@Sparkle I'm curious what response your team has to this poll. Not much has been said, but it's clear people do not want the change. Will this be reverted or adjusted in some way?

 

[sociopathix]

You seem like you have a wonderful personality thank you for your contribution to the discussion.

And thank you. Your total lack of knowledge of how things actually work inspired me to join in.

 

[Sparkle]

The recent change with the guild leaving cooldowns was made due to 2 reasons:​

- to stop guilds from abusing sieges mechanics.​

- as a part of the game data merging with our another server that we had recently.​

​

Now to details:​

​

Siege is originally made as a battle guild vs guild and what players are now doing is jumping from one guild to another to go around that system. That results to some half inactive/dead guilds owning the castles and not leaving guilds with more active players a chance.​

What players now complain about is that they can no longer abuse the mechanics and move between the guilds for sieges. You are currently just asking to let you keep using that abuse and that is not what can we agree to.​

Some players mentioned that they joined other guild for sieges just to have some fun. Then, if players are interested in joining sieges even being a guildless member or a part of another guild, we may think on implementing some kind of custom “Mercenary System” where individuals will be able to choose a side they want to assist during the sieges.​

​

Now to the second reason I mentioned above - game data merging with our another server. That was made for us to be able to work on more updates. As both servers will receive all the same updates, so that will not need the double work done from the devs team side. The update related to the 4 days cooldown was implemented on our RU/EU server long time ago and during the game data merging it didn’t properly went through. This bug was noticed only recently and fixed on our RU/EU server a week ago. Update was auto-applied on our NA server after as server now follow the same updates.​

​

And with this change characters that never left any guilds before also received a pleasant bonus – first time they leave the guild they get no cooldown.​

 

[HNIC_Steamroller]

The recent change with the guild leaving cooldowns was made due to 2 reasons:​

- to stop guilds from abusing sieges mechanics.​

- as a part of the game data merging with our another server that we had recently.​

Now to details:​

Siege is originally made as a battle guild vs guild and what players are now doing is jumping from one guild to another to go around that system. That results to some half inactive/dead guilds owning the castles and not leaving guilds with more active players a chance.​

What players now complain about is that they can no longer abuse the mechanics and move between the guilds for sieges. You are currently just asking to let you keep using that abuse and that is not what can we agree to.​

Some players mentioned that they joined other guild for sieges just to have some fun. Then, if players are interested in joining sieges even being a guildless member or a part of another guild, we may think on implementing some kind of custom “Mercenary System” where individuals will be able to choose a side they want to assist during the sieges.​

Now to the second reason I mentioned above - game data merging with our another server. That was made for us to be able to work on more updates. As both servers will receive all the same updates, so that will not need the double work done from the devs team side. The update related to the 4 days cooldown was implemented on our RU/EU server long time ago and during the game data merging it didn’t properly went through. This bug was noticed only recently and fixed on our RU/EU server a week ago. Update was auto-applied on our NA server after as server now follow the same updates.​

And with this change characters that never left any guilds before also received a pleasant bonus – first time they leave the guild they get no cooldown.​

The problem with this change is it'll allow players to stack into a single guild to attack in sieges but not allow guilds to stack into a guild to defend. It's an imbalanced system and the votes here clearly demonstrate the lack of player support for this change.

 

[trapwhre02]

Yeah I see the same flaw as Dahmer. Your server will just end up in PN and all of east stack into <Casual Gaming Community> or another guild, and siege west every 2 weeks without them being able to defend themselves if they don't want to waste days dropping in advance every single time.

 

[bplease]

The recent change with the guild leaving cooldowns was made due to 2 reasons:​

- to stop guilds from abusing sieges mechanics.​

- as a part of the game data merging with our another server that we had recently.​

Now to details:​

Siege is originally made as a battle guild vs guild and what players are now doing is jumping from one guild to another to go around that system. That results to some half inactive/dead guilds owning the castles and not leaving guilds with more active players a chance.​

What players now complain about is that they can no longer abuse the mechanics and move between the guilds for sieges. You are currently just asking to let you keep using that abuse and that is not what can we agree to.​

Some players mentioned that they joined other guild for sieges just to have some fun. Then, if players are interested in joining sieges even being a guildless member or a part of another guild, we may think on implementing some kind of custom “Mercenary System” where individuals will be able to choose a side they want to assist during the sieges.​

Now to the second reason I mentioned above - game data merging with our another server. That was made for us to be able to work on more updates. As both servers will receive all the same updates, so that will not need the double work done from the devs team side. The update related to the 4 days cooldown was implemented on our RU/EU server long time ago and during the game data merging it didn’t properly went through. This bug was noticed only recently and fixed on our RU/EU server a week ago. Update was auto-applied on our NA server after as server now follow the same updates.​

And with this change characters that never left any guilds before also received a pleasant bonus – first time they leave the guild they get no cooldown.​

Pretty sure this encourages alts with ayanad/erenor sets/weapons...doesn't actually resolve the issues. Just make as many alt toons as there are castles on your side and get yourself a tradable set. Punishes users that went obsidian, nothing else.

 

[plamp]

Pretty sure this encourages alts with ayanad/erenor sets/weapons...doesn't actually resolve the issues. Just make as many alt toons as there are castles on your side and get yourself a tradable set. Punishes users that went obsidian, nothing else.

Be careful! Instead of reverting all the god awful changes they've made regarding sieges they might make ayanad/erenor bind on equip to "stop guilds from abusing siege mechanics."

 

[Aviendha]

This amount of cooldown means people who wants to participate on siege cicles are forced to be 8 days without guild losing a huge amount of prestige and not being abled to take guildflares if it required for pvp, i see no beneficts for any side

not only that, but seeing as siege is every 2 weeks, and if siege actually happens every 2 weeks, you'd be guildless for most of the time.