green_villain wrote: »one of my officers changed his name
robbed all my bank
and then changed name back
i dont know who it was also Zenimax support wont help too = they wont tell me who is the real thief, his @id
i told him @id in guild history doesnt exist anymore but only answer i got was
its normal that Zenimax encourages robbery?
green_villain wrote: »one of my officers changed his name
robbed all my bank
and then changed name back
i dont know who it was also Zenimax support wont help too = they wont tell me who is the real thief, his @id
i told him @id in guild history doesnt exist anymore but only answer i got was
its normal that Zenimax encourages robbery?
ask for ur stuff back but dont ask for the name of the person. this is a difficult case since it was ur decision to make that person an officer and give him access to ur bank. who would do that ? havin ur guildbank open for people that u dont know well is a big mistake. they cant give u the name becouse of privacy rules.
seriously tho what did u write them to get such answer. writing u "are up to the guild to decide" when ur the guild leader. a guild is a monarchy.
green_villain wrote: »one of my officers changed his name
robbed all my bank
and then changed name back
i dont know who it was also Zenimax support wont help too = they wont tell me who is the real thief, his @id
i told him @id in guild history doesnt exist anymore but only answer i got was
its normal that Zenimax encourages robbery?
Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
redspecter23 wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
But the tools are not sufficient in this case. A player was able to bypass the in game records by changing their name. The GM has no access to the changed name. I'd say that is the definition of insufficient tools. Now if the records kept track of the name dynamically or if there were a record of the name change, the guild could take actions against the player. This isn't just about someone taking things from the guild bank. It's about not knowing who did it. The tools are in place to know, but the ability to change your @ name back and forth bypasses that knowledge. I'd say that's a glaring oversight, especially if ZOS can't assist on their end and let the GM know the name of the player that accessed the bank (which should be tracked in the logs normally).
redspecter23 wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
But the tools are not sufficient in this case. A player was able to bypass the in game records by changing their name. The GM has no access to the changed name. I'd say that is the definition of insufficient tools. Now if the records kept track of the name dynamically or if there were a record of the name change, the guild could take actions against the player. This isn't just about someone taking things from the guild bank. It's about not knowing who did it. The tools are in place to know, but the ability to change your @ name back and forth bypasses that knowledge. I'd say that's a glaring oversight, especially if ZOS can't assist on their end and let the GM know the name of the player that accessed the bank (which should be tracked in the logs normally).
Sorry but the tools are, an untrustworthy player was made an officer and it appears from the OP post several officers could be the culprit. This speaks to poor control of who has access to the guild bank. That is not a ZOS issue, that is a personal issue.
Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
green_villain wrote: »one of my officers changed his name
robbed all my bank
and then changed name back
i dont know who it was also Zenimax support wont help too = they wont tell me who is the real thief, his @id
i told him @id in guild history doesnt exist anymore but only answer i got was
its normal that Zenimax encourages robbery?
green_villain wrote: »one of my officers changed his name
robbed all my bank
and then changed name back
i dont know who it was also Zenimax support wont help too = they wont tell me who is the real thief, his @id
i told him @id in guild history doesnt exist anymore but only answer i got was
its normal that Zenimax encourages robbery?
Low blow, yes, but your fault for not choosing better people. It's something common in my profession, this kind of accountability. If someone under your orders screws up, it's your fault. Plain and simple. You chose them, you gave them powers, you told them how it goes, it's on you to choose the right ones for the job.
One can't tell who is who over the internet, so it's up to you to decide if you're taking the risk or doing everything alone. Some people do it alone, btw. Your choice.
I'm really sorry, btw, but yeah... Life lesson, being a cynic is a life saver. Everyone sucks, and until double proven otherwise, everyone is out to get you, and they will if you let them.
MLGProPlayer wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
How were the tools sufficient in this case?
OP wants to figure out who stole the items but they can't because the tools don't provide that information.
MLGProPlayer wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
How were the tools sufficient in this case?
OP wants to figure out who stole the items but they can't because the tools don't provide that information.
OP gave access to a thief, it is that simple. I am GM in 1 guild, a senior officer in another and an officer in a third guild. All three keep a very tight access on the guild bank and gold. It is that simple. Incovienent at times but still easy to avoid even with ESO guild tools.
green_villain wrote: »redspecter23 wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
But the tools are not sufficient in this case. A player was able to bypass the in game records by changing their name. The GM has no access to the changed name. I'd say that is the definition of insufficient tools. Now if the records kept track of the name dynamically or if there were a record of the name change, the guild could take actions against the player. This isn't just about someone taking things from the guild bank. It's about not knowing who did it. The tools are in place to know, but the ability to change your @ name back and forth bypasses that knowledge. I'd say that's a glaring oversight, especially if ZOS can't assist on their end and let the GM know the name of the player that accessed the bank (which should be tracked in the logs normally).
Sorry but the tools are, an untrustworthy player was made an officer and it appears from the OP post several officers could be the culprit. This speaks to poor control of who has access to the guild bank. That is not a ZOS issue, that is a personal issue.
its not a personal issue
you will understand when similar will happend to you
no matter how trustworthy your officers will be
redspecter23 wrote: »MLGProPlayer wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
How were the tools sufficient in this case?
OP wants to figure out who stole the items but they can't because the tools don't provide that information.
OP gave access to a thief, it is that simple. I am GM in 1 guild, a senior officer in another and an officer in a third guild. All three keep a very tight access on the guild bank and gold. It is that simple. Incovienent at times but still easy to avoid even with ESO guild tools.
And what would you do in a similar situation? It was never mentioned that the OP didn't completely trust his officers. That is an assumption. You completely trust your officers, but there is never any guarantee this won't happen to you as well. If it does happen, how do you know who took the items? Do you blame all your officers and have them all be punished because of one bad one? What if it were a hack against a player? Trust doesn't even factor in at that point. Again, it's not about someone emptying the bank. It's about someone being held responsible and the proper tools are not in place to allow this.
green_villain wrote: »
redspecter23 wrote: »MLGProPlayer wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
How were the tools sufficient in this case?
OP wants to figure out who stole the items but they can't because the tools don't provide that information.
OP gave access to a thief, it is that simple. I am GM in 1 guild, a senior officer in another and an officer in a third guild. All three keep a very tight access on the guild bank and gold. It is that simple. Incovienent at times but still easy to avoid even with ESO guild tools.
And what would you do in a similar situation? It was never mentioned that the OP didn't completely trust his officers. That is an assumption. You completely trust your officers, but there is never any guarantee this won't happen to you as well. If it does happen, how do you know who took the items? Do you blame all your officers and have them all be punished because of one bad one? What if it were a hack against a player? Trust doesn't even factor in at that point. Again, it's not about someone emptying the bank. It's about someone being held responsible and the proper tools are not in place to allow this.
Honestly when you have a leadership role in life you will understand this is entirely a leadership issue.
This is not a meteor falling out of the sky thing. OP made the choice who to trust, that is the issue.
I agree it sucks but such is life.
redspecter23 wrote: »Sorry, bottom line never give access to a player you have not known and validated to be of worthy character.
ZOS really is not to blame here. The tools are sufficient to prevent this issue.
But the tools are not sufficient in this case. A player was able to bypass the in game records by changing their name. The GM has no access to the changed name. I'd say that is the definition of insufficient tools. Now if the records kept track of the name dynamically or if there were a record of the name change, the guild could take actions against the player. This isn't just about someone taking things from the guild bank. It's about not knowing who did it. The tools are in place to know, but the ability to change your @ name back and forth bypasses that knowledge. I'd say that's a glaring oversight, especially if ZOS can't assist on their end and let the GM know the name of the player that accessed the bank (which should be tracked in the logs normally).
Sorry but the tools are, an untrustworthy player was made an officer and it appears from the OP post several officers could be the culprit. This speaks to poor control of who has access to the guild bank. That is not a ZOS issue, that is a personal issue.