Preface
We reached a good 3rd place in this 133rd brawl. Congratulations!
While we are experiencing some routine brawling, I am enjoying the movement in and also out of our guild. Since there is currently no pressure on the open spots, that is easy to do. I somewhat yearn back for a smaller Guild Hall, and wish we had expanded the Guild Arena first. But at the time, we couldn't foresee the advantage of a larger arena, and the desire for more players was strong. I don't want to complain about that. But more players is always more work, especially if it is only calculating small amounts. After all, without pressure on the last spot, the field remains very close. And if I can assume that someone goes out spontaneously, I like to acknowledge every little amount by noting it down. Because after leaving, the current total is no longer available in the list of members for taking it into account in my notes.
I felt like, the special feature for new players and brawls, which has been repeated here several times so far, fits well into the addendum. I have therefore extended the addendum by adding the point "2.1. New players brawling".
My statistics draft from the 133rd brawl is again pre-published at https://hackmd.io/@anjanida, with 's great support. 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 "blogging together". Later I added to this with "drafts on mobile". If you have not read enough into adding to Hive and being notified through our Hive community, take a look into "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
02/07 03:00 AM CEST - top-up auction ending, one account will be removed (if all spots are filled)
02/06 01:19 PM CEST - left
02/02 10:50 AM CEST - re-joined
[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 | 02/06/23 | 3,461,730 | 30,102 | 115 | 125 | 8/9 | 7/8 | DBH- | |
| 2 | 02/06/23 | 1,800,554 | 18,373 | 98 | 126 | 10 | 15 | ---F | |
| 3 | 02/06/23 | 1,138,060 | 7,390 | 154 | 71 | 5/6 | 3/4 | --H- | |
| 4 | 02/06/23 | 729,810 | 16,218 | 45 | 106 | 8/9 | 7/8 | ---F | |
| 5 | 02/06/23 | 84,906 | 1,602 | 53 | 42 | 4 | 6 | ---F | |
| 6 | 02/06/23 | 26,600 | 475 | 56 | 28 | - | 13 | DBH- | |
| 7 | 02/06/23 | 25,375 | 725 | 35 | 9 | - | - | ---- | |
| 8 | 02/06/23 | 11,883 | 233 | 51 | 27 | 1/2 | 1 | D--- | |
| 9 | 02/06/23 | 10,122 | 482 | 21 | 33 | - | - | ---- | |
| 10 | 02/06/23 | 8,906 | 122 | 73 | 34 | 7 | 5 | ---- | |
| 13 | 02/06/23 | 2,772 | 63 | 44 | 18 | - | - | ---- | |
| 14 | 02/06/23 | 1,000 | 1,000 | 0 | (5) + 1 | - | 10 | --HF | |
| 15 | 02/06/23 | 648 | 24 | 27 | 13 | - | 2 | D--- | |
| - | 02/06/23 | 100 | 50 | 1 | (9) + 2 | - | - | ---- | |
| 18 | @ OPEN | 02/06/23 | - | - | - | - | - | - | ---- |
| 19 | @ OPEN | 02/06/23 | - | - | - | - | - | - | ---- |
| 20 | @ OPEN | 02/06/23 | - | - | - | - | - | - | ---- |
| 21 | @ OPEN | 02/06/23 | - | - | - | - | - | - | ---- |
@ OPEN 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:
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. @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
@anjanida/member-management-addendum-ee6c5f54ab442