Each 11 % beneficiary rewards of this post will go to 
The experiment blossomed. Thanks for participation, there are some early adoptors! We will continue it with the next brawl.
If you'd like to look back at how our experiment came about, read on in our 98th brawl statistics and continuation of experiment.
After some players joined the experiment during the prep stage, there were again three players participating during the combat stage.
The entire table looked like this before I put it into the statistics draft:
Here now is the idea of the experiment: add a level of interaction within our guild that has numerous positive side effects. Ultimately, everyone can see who actually invests attention in a success of our brawl, and in the publicity that develops from it since the beginning of the brawls - without being overly distracted by social media like Discord. This adds a level of interaction that is not demanding, but supportive.
If you don't want to interact, that's fine. However, others may interact more, and you may end up lagging behind the steady growth of our guild. This can ultimately be read in our guild score table. Those who participate in others' blog posts and perhaps develop a desire to blog themselves will be able to reinvest their rewards back into the game. Growth is inevitable by interacting more.
Once again, I will prepare a table in which the Fray assignment can be noted. The address of the table is the same as at the beginning:
https://hackmd.io/@anjanida/rkHz8oANi/edit
If you haven't participated yet, check out my explanations from the first time again, please.
The question arose how the CP value (Collection Power) should be recorded. Here is my perspective:
When you jot down your CP, don't worry too much about jotting down a value with or without rented cards. Without your assistance in noting, I could not know the best time to record the value to include or exclude rented cards. Decide for yourself when to deduce and record the value, and whether or not to include rented cards. The value simply reflects the growth of the account over the time of the statistics. Where there is no rental, volatility is expected to be lower. The value has simply been easily transferable for me and is interesting in the context of Fray selection. If you don't enter a value, I will, and usually before the combat phase begins. Please do not worry too much about accuracy. In the end, it's just a statistic, and no one should trust a statistic they haven't collected themselves, right?
Another thing that stood out was different ideas about when is a good time to edit the table. Here is my perspective:
The open table is meant for reflecting actual assignments and preparing the results table. If you put something in there before you are actually assigned to the listed Fray, we can read your preference from that even before the brawl has actually started. But don't expect this to actually be implemented then. Only you can make sure that you are assigned to a Fray. If I happen to see your entry in the table before someone else has assigned themselves to the Fray, I can gladly consider the entry. But I expressly don't want to promise that. For that there is the favorite and the possibility to claim it against others, in case you don't manage to assign yourself on time once a brawl has started.
Congratulations to 
Please continue focus your contributions primarily to the Arena and secondarily to the Store. This prioritization is additionally always updated and mentioned in our About section.
My statistics draft from the 116th brawl is again pre-published at https://hackmd.io/@anjanida You are welcome to add your battles to it for becoming a beneficiary when it is published final.
11/07 15:00 AM CEST - top-up auction canceled, because we already have an open spot
11/07 11:27 AM CEST - 
11/05 07:31 AM CEST -
11/0? ??:?? ?? CEST -
11/03 11:06 PM CEST -
[previous timetable]
Actively contributing accounts within the recent blawl and its position by score:
| Spot | Account | Calculated on | Score | DEC | Scrolls | Times brawled | favorite Tier 1 | f/T 2 | reachable via |
|---|---|---|---|---|---|---|---|---|---|
| 1 |  | 10/22/22 | 2,858,976 | 29,781 | 96 | 109 | 8/9 | 7/8 | DBH- |
| 3 |  | 10/22/22 | 862,988 | 7,252 | 119 | 56 | 5/6 | 3/4 | --H- |
| 4 |  | 10/22/22 | 631,566 | 16,194 | 39 | 90 | 5/6 | 3/4 | ---F |
| 5 |  | 11/07/22 | 64,722 | 1,541 | 42 | 26 | 4 | 6 | ---F |
| 6 |  | 11/07/22 | 64,704 | 674 | 96 | 50 | 1/2 | 7/8 | D--- |
| 7 | | 11/07/22 | 9,500 | 500 | 19 | 13 | - | - | ---- |
| 8 | | 11/07/22 | 8,400 | 420 | 20 | 16 | - | - | ---- |
| 9 | | 11/07/22 | 7,220 | 380 | 19 | 15 | - | - | ---- |
| 10 |  | 11/07/22 | 6,720 | 320 | 21 | 12 | - | - | DB-- |
| 11 |  | 11/07/22 | 3,700 | 100 | 37 | 18 | 7 | 5 | ---- |
| 12 |  | 11/07/22 | 3,120 | 130 | 24 | 14 | - | - | ---- |
| 13 |  | 11/07/22 | 2,900 | 290 | 10 | 8 | - | - | ---- |
| 14 | | 11/07/22 | 2,100 | 300 | 7 | - | - | - | ---- |
| 15 | | 11/07/22 | 1,254 | 38 | 33 | 19 | - | 3/4 | D--- |
| - | | 11/02/22 | 1,116 | 124 | 9 | 8 | 1/2 | 1 | ---- |
| 16 | | 11/07/22 | 1,150 | 230 | 5 | 4 | - | - | DB-- |
| 17 | | 11/07/22 | 912 | 38 | 24 | 13 | - | - | ---- |
| 18 | | 11/07/22 | 240 | 60 | 4 | 3 | - | - | ---- |
| 20 | | 11/07/22 | 50 | 50 | 1 | 1 | - | - | ---- |
| 21 | @ OPEN | 11/07/22 | 0 | 0 | - | - | - | - | ---- |
@ no one scheduled for removal
Yellow card: Passive accounts with no DEC or Scroll contribution within the recent blawl (more then 5 days), position by scrolls:
| Spot | Account | Calculated on | Score | DEC | Scrolls | Times brawled | Days ago | Tier 1 favorite | Tier 2 fav | reachable via |
|---|---|---|---|---|---|---|---|---|---|---|
| 2 |  | 11/07/22 | 1,561,705 | 18,373 | 85 | 110 | 6 | 13 | 15 | ---F |
| 19 |  | 11/07/22 | 180 | 60 | 3 | 1 | 6 | - | - | ---- |
Second yellow card: Passive accounts with no DEC or Scroll contribution within a second blawl, position by scrolls:
-- none
Red card: Passive accounts with no DEC or Scroll contribution for more then two blawls, and therefore scheduled for removal, position by scrolls:
-- none
For more recent notes an unofficial draft is at https://hackmd.io/@anjanida
Become familiar with the member management, please. Because the guild spots are precious, the last in our list will be removed regularly. That is part of our procedure as noted in the addendum linked at the bottom. And if you don't acknowledge all this within the first 2 hours after you joined, you may be removed without notice right away. How can we know? Well, you'll see! And any questions are welcome anytime!
Please understand, it is not on me to show comprehension. I'll do the best I can! Though this guild is somewhat managed like a DAO. That is Decentral Autonomous Organisation. So I simply follow the procedures that have evolved here by now. And for when you become passive and no one can reach out to you in time, ugly things can happen. As documented in past notes. See e.g. @anjanida/member-management-notes-defc067f6e74f
If you want to join and stay, we can make that happen even with presently no open spot available. We may schedule it for that you can be there the moment our weakest contributor is removed. Sounds familiar somehow? Like with a mob abandoning their weakest offspring to survive a predator attack. Your contribution needs to be enough for not being the weakest. Everyone who got removed is welcome any time again. It's just that contributions from earlier are at zero any time an account re-joines.
Priority A: Some contribution within the last 3 brawls. Without at least 1 DEC even a quest scroll will make this, if the Lodge is not maxed out for the rest of a season.
Priority B: Be not the weakest contributor in our mob the moment an auction ends. This moment is when a new brawl starts. The second to last score in the list is bold highlighted. That is the tide you need to take in DEC without scrolls added to the lodge yet for outpacing that account.
For our recent Member Management Notes Addendum with general guidelines and procedures see
@anjanida/member-management-addendum
