Member Management Report

Preface

Congratulations to @m0ssa99 for outpacing @zenokrom and corgratulations to @zekken555 for outpacing @mr-inc in our guild score table. @zekken555, you contributed after me asking for becoming more talkative in the chat. So you let the tokens speak for you. Well then. I'm for consistency, so looking forward to see you around - and sending in teams when assingned to a fray.

For everyone to remember: We have a first half of a prep stage and a second half. Don't be so sure about what you catch within the first and come back near the end of preparation to be sure about who's actually brawling. For more on that read the post on Prep Shades, please.

My statistics draft from the 130th brawl is again pre-published at https://hackmd.io/@anjanida, with @anjadani'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 our 109th brawl statistics and blogging together. Later I added to this with our 113th brawl statistics and drafts on mobile. 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/23 01:00 AM CEST - top-up auction ending, one account will be removed (if all spots are filled)
01/21 02:27 AM CEST - @mastermage removed because of ignoring this text
01/20 09:27 PM CEST - @mastermage 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	@anjanida	01/22/23	3,371,424	30,102	112	122	8/9	7/8	DBH-
2	@sm-rules	01/22/23	1,745,435	18,373	95	123	10	15	---F
3	@sodom-lv	01/22/23	1,090,760	7,370	148	68	5/6	3/4	--H-
4	@anjadani	01/22/23	664,856	16,216	41	103	8/9	7/8	---F
5	@annijada	01/22/23	79,750	1,595	50	39	4	6	---F
6	@zeeshannaqvi9th	01/22/23	23,500	470	50	25	-	13	DBH-
7	@untzuntzuntz	01/22/23	23,100	700	33	6	-	-	----
8	@zeeshannaqvi7th	01/22/23	12,920	380	34	16	-	14	DBH-
9	@m0ssa99	01/22/23	10,718	233	46	24	1/2	1	D---
10	@zenokrom	01/22/23	9,933	473	21	30	-	-	----
11	@xcryptogamer	01/22/23	8,040	120	67	31	7	5	----
13	@zekken555	01/22/23	2,754	306	9	10	-	-	----
14	@mr-inc	01/22/23	2,014	53	38	16	-	-	----
16	@huuczu	01/22/23	462	22	21	10	-	2	----
17	@deecee777	01/22/23	250	50	5	3	-	-	D---
19	@ OPEN	01/22/23	-	-	-	-	-	-	----
20	@ OPEN	01/22/23	-	-	-	-	-	-	----
21	@ OPEN	01/22/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:

Spot	Account	Calculated on	Score	DEC	Scrolls	Times brawled	Days ago	Tier 1 favorite	Tier 2 fav	reachable via
12	@ldrwndozuvoxeiny	01/22/23	4,508	4,508	0	1	16	-	-	----

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
15	@shadowzekken	01/22/23	300	60	5	4	22	-	-	----
18	@iyel25	01/22/23	20	20	0	-	59	-	-	----

@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