Member Management Report
Each 10 % beneficiary rewards of this post will go to most players who sent teams this brawl. (I did not know that there is a maximum of eight beneficiaries at a time.) For more see the latest post on Beneficiaries.
Preface
Lots of players not sending their teams this time, me included. What can I say. I'll note more in our statistics post on this 127th brawl. Now to the management.
Congratulations to @zeeshannaqvi7th for outpacing @zenokrom and @m0ssa99 in our guild score table.
My statistics draft from the 127th brawl is again pre-published at https://hackmd.io/@anjanida, with @anjadani's support following tomorrow for sure. You are welcome to add to it, too, i.e. with your battle links and some short commentary to it, for becoming a beneficiary when it is published final. It is just that this draft at HackMD is not public for anonymous editing but needs you to sign-in with your individually registered account.
Ultimately, I want to facilitate the access to planning and drafting of articles in order to levitate individual blogging. If you haven't participated yet, check out our 109th brawl statistics and blogging together. If you have not read enough into adding to Hive and being notified through our Hive community, take a look into our 108th brawl statistics and Discord bot update.
Index
- Timetable
- Internal Player Score Table
- If you are new to this
- What we expect from any member, in a nutshell
- Link to addendum
Timetable
01/05 10:00 PM CEST - next brawl starts, no auction necessary [previous timetable]
Internal Player Score Table
Actively contributing accounts within the recent blawl and its position by score:
| Spot | Account | Calculated on | Score | DEC | Scrolls | Times brawled | favorite Tier 1 | favorite Tier 2 | reachable via |
|---|---|---|---|---|---|---|---|---|---|
| 1 | @anjanida | 01/05/23 | 3,243,780 | 30,035 | 108 | 119 | 8/9 | 7/8 | DBH- |
| 2 | @sm-rules | 01/05/23 | 1,690,316 | 18,373 | 92 | 120 | 10 | 15 | ---F |
| 3 | @sodom-lv | 01/05/23 | 1,051,050 | 7,350 | 143 | 65 | 5/6 | 3/4 | --H- |
| 4 | @anjadani | 01/05/23 | 664,651 | 16,211 | 41 | 100 | 8/9 | 7/8 | ---F |
| 5 | @annijada | 01/05/23 | 76,464 | 1,593 | 48 | 36 | 4 | 6 | ---F |
| 6 | @zeeshannaqvi9th | 01/05/23 | 19,565 | 455 | 43 | 22 | - | 13 | DBH- |
| 7 | @untzuntzuntz | 01/05/23 | 16,250 | 650 | 25 | 5 | - | - | ---- |
| 8 | @zeeshannaqvi7th | 01/05/23 | 10,220 | 365 | 28 | 13 | - | 14 | DBH- |
| 9 | @zenokrom | 01/05/23 | 9,597 | 457 | 21 | 27 | - | - | ---- |
| 10 | @m0ssa99 | 01/05/23 | 8,610 | 210 | 41 | 21 | 1/2 | 1 | D--- |
| 11 | @xcryptogamer | 01/05/23 | 6,954 | 114 | 61 | 28 | 7 | 5 | ---- |
| 12 | @mr-inc | 01/05/23 | 1,643 | 53 | 31 | 16 | - | - | ---- |
| 15 | @shadowzekken | 01/05/23 | 300 | 60 | 5 | 3 | - | - | ---- |
| 16 | @huuczu | 01/05/23 | 300 | 20 | 15 | 7 | - | - | ---- |
| 18 | @ OPEN | 01/05/23 | - | - | - | - | - | - | ---- |
| 19 | @ OPEN | 01/05/23 | - | - | - | - | - | - | ---- |
| 20 | @ OPEN | 01/05/23 | - | - | - | - | - | - | ---- |
| 21 | @ OPEN | 01/05/23 | - | - | - | - | - | - | ---- |
@ no one scheduled for removal, if no passive account is going to be removed.
Yellow card: Passive accounts with no DEC or Scroll contribution within the recent blawl (more then 5 days), position by scrolls:
-- none
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:
| Spot | Account | Calculated on | Score | DEC | Scrolls | Times brawled | Days ago | Tier 1 favorite | Tier 2 fav | reachable via |
|---|---|---|---|---|---|---|---|---|---|---|
| 14 | @zekken555 | 01/05/23 | 742 | 106 | 7 | 8 | 18 | - | - | ---- |
| 13 | @ldrwndozuvoxeiny | 01/05/23 | 400 | 400 | 0 | - | 34 | - | - | ---- |
| 17 | @iyel25 | 01/05/23 | 20 | 20 | 0 | - | 42 | - | - | ---- |
@iyel25 scheduled for removal for being passive, if there is no open spot.
For more recent notes an unofficial draft is at https://hackmd.io/@anjanida
If you are new to this
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. https://peakd.com/@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.
What we expect from any enduring member, in a nutshell:
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. Just keep in mind that this is going to be a live auction, so whatever other accounts put into it within the last seconds is summed up to be the final result, no matter what this published report showed some minutes or sometimes days before. Only the result is published again afterwards.
Link to addendum
For our recent Member Management Notes Addendum with general guidelines and procedures see
https://peakd.com/hive-179856/@anjanida/member-management-addendum
