I'd like to bring up something about how AC is currently done that I was reminded of during this last AC round and which I find to be needlessly rigid within the AC system.
Currently, the rule is that if you have a thread going in a log that was posted in the previous month, you may continue to tag it into the new month and have any tags from that count for AC. But you cannot create a new thread within the new month in a log (essentially a top level or responding to a top level) and have that count toward AC EVEN IF the log in question is supposed to cover time that takes place in both months.
The differences between continuing a thread and starting a new top level in a log that is dated for the correct month ICly is minimal. I don't see the point to having this rule. So long as the same thread is not presented as AC proof in both months, and no one is trying to start a top level in a log that's not part of the 'current' game state (a log that takes place across the previous month and the current month is still part of the 'current' game state), there really shouldn't be a need for such a rigid rule to be in place.
Posting to a log that bridges the previous month and the current month (or current month and upcoming month) should be allowed to count for AC so long as the tags fall within the AC period in question. It allows for better organization and grouping of logs and events without spamming the comm with what is essentially a repeat of the original group log just to ensure you can count it for AC if you want it to.
If it's a worry about someone abusing the system, simply put in a 'common sense' ruling - IE, it's common sense that you can't tag into a log from December with a new top level and thread things out and have it count for AC because you aren't actually being active in the current game state - to cover any concerns on that end.
Otherwise, I find the AC system to be perfectly acceptable. This one part of it just makes no real sense to be so hard-lined on in my opinion.
Re: MODS
Currently, the rule is that if you have a thread going in a log that was posted in the previous month, you may continue to tag it into the new month and have any tags from that count for AC. But you cannot create a new thread within the new month in a log (essentially a top level or responding to a top level) and have that count toward AC EVEN IF the log in question is supposed to cover time that takes place in both months.
The differences between continuing a thread and starting a new top level in a log that is dated for the correct month ICly is minimal. I don't see the point to having this rule. So long as the same thread is not presented as AC proof in both months, and no one is trying to start a top level in a log that's not part of the 'current' game state (a log that takes place across the previous month and the current month is still part of the 'current' game state), there really shouldn't be a need for such a rigid rule to be in place.
Posting to a log that bridges the previous month and the current month (or current month and upcoming month) should be allowed to count for AC so long as the tags fall within the AC period in question. It allows for better organization and grouping of logs and events without spamming the comm with what is essentially a repeat of the original group log just to ensure you can count it for AC if you want it to.
If it's a worry about someone abusing the system, simply put in a 'common sense' ruling - IE, it's common sense that you can't tag into a log from December with a new top level and thread things out and have it count for AC because you aren't actually being active in the current game state - to cover any concerns on that end.
Otherwise, I find the AC system to be perfectly acceptable. This one part of it just makes no real sense to be so hard-lined on in my opinion.
Thank you