Member Management Notes

Words
919
Reading
5 min
Listen
Play
4y

Preface

Starting from the next brawl, I want to extend the grace period before removal due to passivity. It will be the duration of one more brawl, i.e. 5 to 6 days (depending on how long the result phase is). This makes activity possible without contributing DEC, provided the lodge is not maxed out, because three brawls are about the length of a season.

The background is that DEC contributions are now only possible if the player is in possession of the Hive active key. This was not always the case. Scrolls, however, can be contributed if a player only has the posting key. This is unfortunately the case at least for sm-rules@sm-rules. And it should not be a reason that the account cannot remain active.

I hope this will benefit more players. With the guild's goal of making the name visible, this is quite compatible. I hope DEC contributions remain attractive due to internal ranking. Outranking sm-rules@sm-rules can be a rewarding challenge in this regard. The extra effort of listing passive accounts seems tolerable to me, and all players get another level of warning before removal is imminent. If anyone has a better idea to manage activity, please speak up.

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

09/11 01:00 AM CEST - top-up auction ending, one account will be removed (if all spots are filled)
09/10 12:55 AM CEST - daymonds@daymonds joined
09/09 07:57 PM CEST - schwii000@schwii000 removed because of ignoring this text
09/09 01:36 AM CEST - schwii000@schwii000 joined
09/08 10:36 PM CEST - unimax-001@unimax-001 removed because of ignoring this text
09/08 05:18 PM CEST - unimax-001@unimax-001 joined
09/07 12:03 PM CEST - pyrekid@pyrekid removed because of ignoring this text
09/07 03:45 AM CEST - pyrekid@pyrekid joined
09/06 10:16 PM CEST - cb5splinterland@cb5splinterland removed because of ignoring this text
09/06 07:18 PM CEST - cb5splinterland@cb5splinterland joined
09/06 05:50 PM CEST - aghilyx55@aghilyx55 removed because of ignoring this text
09/06 02:15 AM CEST - aghilyx55@aghilyx55 joined
09/05 10:53 PM CEST - nlzqnlzq533@nlzqnlzq533 removed because of ignoring this text
09/05 01:13 PM CEST - nlzqnlzq533@nlzqnlzq533 joined
[previous timetable]

Internal Player Score Table

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

SpotAccountCalculated onScoreDECScrollsTimes brawledfavorite Tier 1f/T 2
1anjanida@anjanida07/25/222,341,20029,26580988/97/8
2sm-rules@sm-rules08/30/221,322,85618,37372991315
3sodom-lv@sodom-lv07/25/22582,5186,19794565/63/4
4anjadani@anjadani08/20/22566,23016,17835795/63/4
5tld05@tld0508/30/22131,6701,386957132
6eika@eika09/05/22112,7492,30149221/21
7mervol@mervol08/14/2275,8161,4585220--
8ykyan2@ykyan209/10/2251,63666278391/27/8
9annijada@annijada09/10/2248,7741,478331546
10zenokrom@zenokrom09/05/224,815321157--
14xcryptogamer@xcryptogamer09/05/221,19070177--
15ericohrn@ericohrn09/05/2272018042--
12phantomx123@phantomx12309/05/223,10534595--
17ykyan4@ykyan409/10/2248030168-3/4
19m0ssa99@m0ssa9909/10/221803064--
21daymonds@daymonds09/10/2210100---

daymonds@daymonds scheduled for removal, if all accounts are active for more then the recent brawl.

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 fav
16zeeshannaqvi9th@zeeshannaqvi9th09/10/22600200316--

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

SpotAccountCalculated onScoreDECScrollsTimes brawledDays agoTier 1 favoriteTier 2 fav
18mr-inc@mr-inc09/10/222701815411--
13xrypto202084@xrypto20208409/10/221,4801858512--
11amburst@amburst09/10/223,3005506311--
20aaustino2@aaustino209/10/2277770414--

aaustino2@aaustino2 scheduled for removal, 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 2 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
@anjanida/member-management-notes-addendum-rd1515

Member Management Notes | Ecency