daily raid ticket issue! how to track members contribution?

FYI

I found if I kill SWOGH and restart/login after guild reset the "manage" counter will work properly.

"sying;952598" wrote:

"SnakesOnAPlane;952542" wrote:
Why don't y'all just make it easier on yourselves? Remove everyone from the guild after a reset, then bring them right back. The process takes about 20 min total. I created a spreadsheet with all guild members' ally codes To make it quick and seamless. Each officer handled about 6-8 each during the boot and bring-back. It was very simple.

From then on, the lifetime tickets are always divisible by 600. You can easily see who is short prior to reset and message them to get it handled. As soon as they miss, you boot and bring right back (takes about 1 min). We have a 3-strike rule within so many months (leader discretion, since things happen - we also have a channel when folks will be out and can't get their 600). All offenses are kept private in a Leader channel on Discord. Since we did this, our 30K days went up dramatically. We now hit it about 99% of the time.

Now no one can fake, or claim they didn't realize they hadn't hit 600.

We only allow two offenses. The first one, they're booted and then can rejoin. We use an alt to quickly fill the 600. The second one, they're gone. People have come back after a hiatus or come back to one of our other guilds. We've hit 30k every day for I don't even remember how long.

@Sifusan I was in a guild that required screenshots. I've never missed hitting 600. I did miss submitting a pic once because I usually play in the early mornings. I was working a lot of hours, not getting a lot of sleep, and just plain forgot to take and submit a picture of my 600. I was given a warning and told that if I did it again I would be removed. Not for missing 600 which is way more important but because I didn't take a pic. It was then I knew I needed to move on. KISS. Keep it simple and so on. There's no need for submitting pics when the game provides two trackers. Just don't use the broken one.

Yeah submitting a screenshot is really annoying.
Leaving and joining back is a good idea.

If your guild is a strict 600 a day @SnakesOnAPlane suggestion is the way to go
If it's not you only way is a spreadsheet where you take the lifetime score at exactly guild reset

"Ztyle;954469" wrote:
If your guild is a strict 600 a day @SnakesOnAPlane suggestion is the way to go
If it's not you only way is a spreadsheet where you take the lifetime score at exactly guild reset

That second option is way more work tho. Once the boot and bring back takes place then it's easy greasy from then on out.

"sying;952598" wrote:

"SnakesOnAPlane;952542" wrote:
Why don't y'all just make it easier on yourselves? Remove everyone from the guild after a reset, then bring them right back. The process takes about 20 min total. I created a spreadsheet with all guild members' ally codes To make it quick and seamless. Each officer handled about 6-8 each during the boot and bring-back. It was very simple.

From then on, the lifetime tickets are always divisible by 600. You can easily see who is short prior to reset and message them to get it handled. As soon as they miss, you boot and bring right back (takes about 1 min). We have a 3-strike rule within so many months (leader discretion, since things happen - we also have a channel when folks will be out and can't get their 600). All offenses are kept private in a Leader channel on Discord. Since we did this, our 30K days went up dramatically. We now hit it about 99% of the time.

Now no one can fake, or claim they didn't realize they hadn't hit 600.

We only allow two offenses. The first one, they're booted and then can rejoin. We use an alt to quickly fill the 600.

Why use an alt account? They should be booted the moment after payout and then brought immediately back. They then have 24 hours again to get the next 600. The alternate should only come into play after a permanent boot while waiting on a new member.

2 offenses is rough, lol. Especially when there are plenty of Raid tickets in reserve after that so as not to miss the next raid for weeks or months on end.

This has been a issue from the start of guilds. Too many of the numbers are dependant on when the guild leader last logged in, the guild reset time, and the last time the member logged in. But anytime someone complains you get responses that say its fine if you check at this time or do a guild wipe or some other set of hurdles. The point is the counters should work period, independant of a dozen login factors. And you should not have to do a guild reset or other "simple" hurdles to get it to work. I basically just check the lifetime contributions and gauge against how long they have been in the guild. If they arent doing at least half (300) then they arent pulling their weight. I also have a 2 day inactivity rule. Between the two we keep a pretty active roster of 40 to 45 members. Im hoping they give the guild manage section some love soon.

"Kronen;956093" wrote:
This has been a issue from the start of guilds. Too many of the numbers are dependant on when the guild leader last logged in, the guild reset time, and the last time the member logged in. But anytime someone complains you get responses that say its fine if you check at this time or do a guild wipe or some other set of hurdles. The point is the counters should work period, independant of a dozen login factors. And you should not have to do a guild reset or other "simple" hurdles to get it to work. I basically just check the lifetime contributions and gauge against how long they have been in the guild. If they arent doing at least half (300) then they arent pulling their weight. I also have a 2 day inactivity rule. Between the two we keep a pretty active roster of 40 to 45 members. Im hoping they give the guild manage section some love soon.

300?! Wow y'all must hardly ever raid. One can get that within 1 min just by simming their daily regenerated energy after waking.

Wow all of this effort to monitor daily contribution. I guess its too much to ask that two sets of numbers add up.. its completely ridiculous that the guild management tools don't work.

This is by far my biggest frustration as a guild leader.

"SnakesOnAPlane;956073" wrote:

"sying;952598" wrote:

"SnakesOnAPlane;952542" wrote:
Why don't y'all just make it easier on yourselves? Remove everyone from the guild after a reset, then bring them right back. The process takes about 20 min total. I created a spreadsheet with all guild members' ally codes To make it quick and seamless. Each officer handled about 6-8 each during the boot and bring-back. It was very simple.

From then on, the lifetime tickets are always divisible by 600. You can easily see who is short prior to reset and message them to get it handled. As soon as they miss, you boot and bring right back (takes about 1 min). We have a 3-strike rule within so many months (leader discretion, since things happen - we also have a channel when folks will be out and can't get their 600). All offenses are kept private in a Leader channel on Discord. Since we did this, our 30K days went up dramatically. We now hit it about 99% of the time.

Now no one can fake, or claim they didn't realize they hadn't hit 600.

We only allow two offenses. The first one, they're booted and then can rejoin. We use an alt to quickly fill the 600.

Why use an alt account? They should be booted the moment after payout and then brought immediately back. They then have 24 hours again to get the next 600. The alternate should only come into play after a permanent boot while waiting on a new member.

2 offenses is rough, lol. Especially when there are plenty of Raid tickets in reserve after that so as not to miss the next raid for weeks or months on end.

Because if you wait until after payout then the whole guild missed hitting 30k for the day and we can't raid as much. Even if we miss it by 1 we have to push both raids back a day.

"sying;956273" wrote:

"SnakesOnAPlane;956073" wrote:

"sying;952598" wrote:

"SnakesOnAPlane;952542" wrote:
Why don't y'all just make it easier on yourselves? Remove everyone from the guild after a reset, then bring them right back. The process takes about 20 min total. I created a spreadsheet with all guild members' ally codes To make it quick and seamless. Each officer handled about 6-8 each during the boot and bring-back. It was very simple.

From then on, the lifetime tickets are always divisible by 600. You can easily see who is short prior to reset and message them to get it handled. As soon as they miss, you boot and bring right back (takes about 1 min). We have a 3-strike rule within so many months (leader discretion, since things happen - we also have a channel when folks will be out and can't get their 600). All offenses are kept private in a Leader channel on Discord. Since we did this, our 30K days went up dramatically. We now hit it about 99% of the time.

Now no one can fake, or claim they didn't realize they hadn't hit 600.

We only allow two offenses. The first one, they're booted and then can rejoin. We use an alt to quickly fill the 600.

Why use an alt account? They should be booted the moment after payout and then brought immediately back. They then have 24 hours again to get the next 600. The alternate should only come into play after a permanent boot while waiting on a new member.

2 offenses is rough, lol. Especially when there are plenty of Raid tickets in reserve after that so as not to miss the next raid for weeks or months on end.

Because if you wait until after payout then the whole guild missed hitting 30k for the day and we can't raid as much. Even if we miss it by 1 we have to push both raids back a day.

You should have reserves to fix this. 1 day of reserves would prevent this entirely @sying