[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85
[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20
New problems with the guild menu not mentioned elsewhere.
As has been noted elsewhere, the new guild suppression/restriction update has caused many problems for guilds, both intentional and unintentional. Since the new member limit for guilds is 100 accounts, and the major guilds on every server had 300 members total, most GMs have been required to kick many of their members to comply with the new rules, or lose their ability to recruit. Compounding this is the lack of any way to identify which players are on which accounts, thus even when GMs do kick, it often results in someone's alt being removed and the account number not decreasing.
Since there is no way to track players by account, and this is such an obvious problem that it must have been considered by staff, I can only assume this was done with the intention of frustrating guild masters.
As major a problem as this is, there has been another change made with the update that compounds this issue, that I am not sure if it was intentional or not.
The guild menu has long been capable of identifying player's activity by noting the last time they logged in. However, it seems this feature has been removed. Instead of identifying WHEN a player last logged, now it can tell us WHERE they logged.
As if guild masters needed to know the last known location of a member for some reason, as opposed to knowing whether they are active or not. Because of this, it has become impossible to kick inactives to comply with the new guild rules. GG.
So, I know what the response to this is going to be. "Check guild contribution instead of activity."
My response to this is: How are RP guilds, social guilds, noob guilds, and even pvp guilds supposed to track then? PvP guild dailies focus on wins, which is great if you are Good Fight. Every one else is screwed due to existing problems with PvP BGs, etc etc. But those problems are outside the scope of this message.
PLEASE GIVE US BACK OUR ABILITY TO TRACK LOGIN DATE THROUGH THE GUILD MENU!!!
Since there is no way to track players by account, and this is such an obvious problem that it must have been considered by staff, I can only assume this was done with the intention of frustrating guild masters.
As major a problem as this is, there has been another change made with the update that compounds this issue, that I am not sure if it was intentional or not.
The guild menu has long been capable of identifying player's activity by noting the last time they logged in. However, it seems this feature has been removed. Instead of identifying WHEN a player last logged, now it can tell us WHERE they logged.
As if guild masters needed to know the last known location of a member for some reason, as opposed to knowing whether they are active or not. Because of this, it has become impossible to kick inactives to comply with the new guild rules. GG.
So, I know what the response to this is going to be. "Check guild contribution instead of activity."
My response to this is: How are RP guilds, social guilds, noob guilds, and even pvp guilds supposed to track then? PvP guild dailies focus on wins, which is great if you are Good Fight. Every one else is screwed due to existing problems with PvP BGs, etc etc. But those problems are outside the scope of this message.
PLEASE GIVE US BACK OUR ABILITY TO TRACK LOGIN DATE THROUGH THE GUILD MENU!!!
1
Comments
This thread used to be stickied General Discussion and it mentioned last location issue.