Spanky Posted July 7, 2009 Report Posted July 7, 2009 Problem -A guild with 30+ people will need a second party, but once PvP is enabled, my guild members started to attack me. That's kinda'.. wrong? since it's Guild vs Guild. -A guild we wanted to work together with (are allies) ended up attacking us. Personally, I have a joint guild which is also Destiny and I don't want to attack it. Suggestion -Switch back to the old GvG settings where allied guilds can't attack each other, and our own guild members can't attack each other. If the old GvG settings won't be allowed, change it a bit so those problems above are gone. What do you guys think?
peterx781 Posted July 7, 2009 Report Posted July 7, 2009 Problem -Switch back to the old GvG settings where allied guilds can't attack each other, and our own guild members can't attack each other. If the old GvG settings won't be allowed, change it a bit so those problems above are gone. What do you guys think? I completely agreee.
rinrin Posted July 7, 2009 Report Posted July 7, 2009 Definitely agree. If you don't want the ally thing, at least fix the guild party thing. If not, at least WARN US ABOUT the change.
FFLASH Posted July 7, 2009 Report Posted July 7, 2009 I think that is a great suggestion and it should be implemented fucking ASAP.
Martin Posted July 7, 2009 Report Posted July 7, 2009 I agree. I was getting hit by people all over, including from our side D: Change it! D:
Groxy Drank Posted July 8, 2009 Report Posted July 8, 2009 Problem -A guild with 30+ people will need a second party, but once PvP is enabled, my guild members started to attack me. That's kinda'.. wrong? since it's Guild vs Guild. -A guild we wanted to work together with (are allies) ended up attacking us. Personally, I have a joint guild which is also Destiny and I don't want to attack it. Suggestion -Switch back to the old GvG settings where allied guilds can't attack each other, and our own guild members can't attack each other. If the old GvG settings won't be allowed, change it a bit so those problems above are gone. What do you guys think? (Problem) Im in a guild that normally GvG with 30+ people it means 2 partys sometimes 3 (depends on the need) and id say that its just organization and the respect they have to each other. About the allies problem they cant make (No allies fire) cuz it means that at the end of the event there will be more than 1 guild at the end of the GvG (it means no winner) i dont want to say that word again but imma have to ITS RESPECT. (Suggestion) I agree with the no guild members fire but its impposible to make the allies stuff just like i said before.
Millenia Posted July 8, 2009 Report Posted July 8, 2009 how about you gms start telling the players WHAT THE FOK YOU GUYS ARE DOING next tiem
kuoch Posted July 8, 2009 Report Posted July 8, 2009 I think that is a great suggestion and it should be implemented fucking ASAP.
Genesis Posted July 8, 2009 Report Posted July 8, 2009 definitely not cool when 4/5 of your guild is taken out by your allies because you just didn't fucking know that you could attack them. dear GMs, stop sucking and not telling us what the fuck happens when you update the server then expect us to just deal with it. Because, certain aspects of the game change when we update our revision, we are not aware of every small change, nor every small bug; it is simply impossible to keep track. We updated not because we wanted to, simply because we had to. Comments like this, and others really are counter productive and are getting old, fast.
Shield Posted July 8, 2009 Report Posted July 8, 2009 The GvG map was one in a long list of maps that we were flagging for PvP combat. It accidentally got changed to where guildmates and alliances could combat each other, instead of just alliances, like all the other maps where PvP happens(anthell,for_fild01,thor,lhz,pvp rooms, etc..). The map will be flagged so that guildmates/alliances can't hurt each other, again. I'll try not to ''suck'' so much in the future but in my defense it was an accident. Sorry for the major inconvenience, it should be fixed now. ~Accepted and completed~