Member Management Report

Epilog

We reached a third place in the 122nd brawl. Congratulations!

I once again want to stress the utility of declaring your favorite, and recent details about it are in a former report. By declaring it in the chat, everyone will be able to perceive this as an activity within the guild. My role here is not to be a coach who anticipates or assigns favorites. My role is DAO management. Declare, you're independent!

Congratulations to @m0ssa99 and @zeeshannaqvi7th for outpacing @xcryptogamer this time in our guild score table.

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.

If you have not read into communications enough, take a look into our 106th brawl statistics and notifications. Even though my son is doing the prep and results table, you can, however, get ahead of him and continue to work with the draft texts. 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 my explanations from the first time again.

My statistics draft from the 122th 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. It is just that this draft is not public for anonymous editing but needs you to sign-in with your individualy registered account.

screenshot_at_2021_12_12_14_43_19_splinterlands_guild_fhree_logo.png

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

12/10 05:00 PM CEST - top-up auction canceled, due to already having an open spot
12/10 04:59 PM CEST - @chidorine removed because of ignoring this text
12/07 04:34 AM CEST - @chidorine joined
12/04 10:24 PM CEST - @felipek left
12/01 08:47 AM CEST - @ldrwndozuvoxeiny joined
12/01 02:47 PM CEST - @naz17tm removed because of ignoring this text
12/01 07:15 AM CEST - @naz17tm joined
11/29 10:31 PM CEST - @huuczu joined
[previous timetable]

Internal Player Score Table

Actively contributing accounts within the recent blawl and its position by score:

SpotAccountCalculated onScoreDECScrollsTimes brawledfavorite Tier 1favorite Tier 2reachable via
1@anjanida12/10/223,048,78029,8901021148/97/8DBH-
3@sodom-lv12/10/22967,8247,332132605/63/4--H-
4@anjadani12/10/22648,32016,20840958/97/8---F
5@annijada12/10/2271,5951,591453146---F
6@zeeshannaqvi9th12/10/2213,7604303217--DBH-
7@zenokrom12/10/229,2194392121------
8@phantomx12312/10/228,3603802219-12----
9@untzuntzuntz12/10/226,400400163------
10@m0ssa9912/10/225,8901903116------
12@zeeshannaqvi7th12/10/225,440340169--DBH-
11@xcryptogamer12/10/225,390110492375----
13@splinter2yop12/10/222,640220126-3/4----
14@mr-inc12/10/221,248482614------
20@huuczu12/10/2210252------
-@chidorine12/10/220001------
21@ OPEN12/10/22----------

@ 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:

SpotAccountCalculated onScoreDECScrollsTimes brawledDays agoTier 1 favoriteTier 2 favreachable via
2@sm-rules12/10/221,635,19718,3738911571015---F
15@ldrwndozuvoxeiny12/10/224004000-8------

Second yellow card: Passive accounts with no DEC or Scroll contribution within a second blawl, position by scrolls:

SpotAccountCalculated onScoreDECScrollsTimes brawledDays agoTier 1 favoriteTier 2 favreachable via
19@iyel2512/10/2220200-16------

Red card: Passive accounts with no DEC or Scroll contribution for more then two blawls, and therefore scheduled for removal, position by scrolls:

SpotAccountCalculated onScoreDECScrollsTimes brawledDays agoTier 1 favoriteTier 2 favreachable via
16@zekken55512/10/22360606521------
17@shadowzekken12/10/22240604224------
18@cloveeer12/10/2227270-20------

@cloveeer 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.

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



0
0
0.000
1 comments