(edited by TnT.8374)
Showing Posts For TnT.8374:
As of at least one day ago, there were several undocumented changes to the Gilded Hollow map. I haven’t seen it mentioned anywhere in the patch notes or the forums as to what was changed and why. Several cool explorable areas of the map have been closed off by newly added rocks or other various blocking objects.
My concern is that some of the areas, such as example one shown in the following screenshots: Imgur Album showing locations were available for placing decorations. It is unknown at this moment if those decorations were refunded (probably not), or if they are now just stuck behind an impassible wall. Without tools to remove decorations on the map you cannot see, this is a huge issue. I also do not understand what the point of blocking off these cool places for people to find is, when someone had to take the time to create them in the first place.
I am not looking for any revert to these changes, I am just looking for reasoning as to why these changes were made and information on what happened to the decorations that were placed in these locations. I can’t tell if they were refunded or not, because I do not know how many of each decoration my guild had before these changes.
(edited by TnT.8374)
Yeah, they’ve been broken for two weeks now.
We had the same issue yesterday, but thankfully I was cautious and only did one of the small boosts.
I completely agree. We had this issue with pvp missions in particular the first week and had to switch to only pve missions instead until it is finished.
I like this idea – minus the diminishing bonuses part.
If there was no cap, or point where you got less influence for each person completing, very large guilds would be getting insane amounts of influence.
The diminishing returns would look something like this, with preferably more influence per person as they’re doing much more than just logging in. Taken from the guildwars2 wiki for influence on attendance:
“Attendance
The game checks once every 24 hours for members who have logged on and represented the guild during the previous 24 hours.
10 per member for the first 20 members.
5 per member from 20 to 50 members.
1 per each additional member"
Several players and guilds have been talking lately about influence generation, and thinking of ideas how a smaller guild can generate enough influence to be able to research guild missions.
My suggestion is to take the newly updated daily system and make is so that when you complete your daily, your guild gains some amount of influence. This would reward guilds for players that are being active and representing their guild while doing their dailies that they have picked to do for the day. To scale, you could also give diminishing bonuses after a certain number of daily completions (as attendance functions currently).
I feel that currently influence rewards guilds of hardcore players that run a lot of dungeons, and guilds with large amounts of people, but not decent sized guilds with more casual players. A more casual player may get on every day and gather, kill some things or do some wvw, but they are generating much less influence then someone running several dungeons. In addition, these casual players may be just as active and engaged in the guild as more hardcore players.
This change would make playing the game the way that you like it still rewarding to your guild members, and wouldn’t take away from any specific type of player.
Thank you for taking the time to read this post. I did some quick searches to see if this had already suggested, but please let me know if this is a duplicate thread so I can remove it.
I have experienced two instances of my entire party getting disconnected at the same exact moment, sending us all back to the character select screen for no known reason. When this happens in a dungeon or other instanced event, this means we have to start over from the beginning as it loses our progress we had made.
The first was 2 days ago while in the Ascalon fractal, and today while doing the Tixx event for the Black Citadel.
I had not experienced this issue before the 12/14/12 patch.