10 % beneficiary rewards of this post will go to @bitcoinzoli this time. For more see the latest post on Beneficiaries.
Preface
We had a hitchhiker for the first time, who showed himself grateful as such for the open spot. That's a thing I expected to happen one day and I don't see a problem with it yet. If someone does see a problem, I'd love to deal with it (screenshot below).
The experiment for mutual documentation with option to being notified of our progress through hackMD keeps going, with some new idea how to incentivise with it. We will continue it with the next brawl.
If you like to trace backwards from where our experiment developed, read on in what was going on this week.
Here again is the idea of the experiment: add a level of interaction within our guild that has numerous positive side effects. Ultimately, everyone can see who actually invests attention in a success of our brawl, and in the publicity that develops from it since the beginning of the brawls. This adds a level of interaction that is not demanding, but supportive.
If you don't want to interact, that's fine. However, others may interact more, and you may end up lagging behind the steady growth and change of our guild. This can ultimately be read in our guild score table. Those who participate in others' blog posts and perhaps develop a desire to blog themselves will be able to reinvest their rewards back into the game easily. Growth is inevitable by interacting more.
Moving on
Once again, I will prepare a table in which the Fray assignment can be noted. The address of the table is still the same as at the beginning:
https://hackmd.io/@anjanida/rkHz8oANi/edit
If you haven't participated yet, check out my explanations from the first time again or trace everything backwards from the link mentioned above, please.
What else?
Congratulations to @zeeshannaqvi9th for outpacing @phantomx123 and to @zeeshannaqvi7th for outpacing @ykyan4 in our guild score table. I am certain in the course of time we will get pressure on the second to last spot again.
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.
My statistics draft from the 117th 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.
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
11/13 10:45 PM CEST - top-up auction canceled, because we have an open spot already
11/13 02:41 PM CEST - @izhy3 removed because of ignoring this text
11/13 01:30 AM CEST - @izhy3 joined
11/11 12:15 PM CEST - @gilli.got.kicked removed because of ignoring this text
11/10 05:49 PM CEST - @gilli.got.kicked joined
11/10 01:38 PM CEST - @baepae removed because of ignoring this text
11/10 07:48 AM CEST - @baepae joined
11/10 ??:?? ?M CEST - @vhin024 left
11/10 03:46 AM CEST - @vhin024 joined
11/09 08:13 PM CEST - @ciskyut removed because of ignoring this text
11/09 04:34 PM CEST - @ciskyut joined
11/09 0?:?? PM CEST - @bm21 left
11/09 01:26 PM CEST - @bm21 joined
11/08 ??:?? PM CEST - @bitcoinzoli left
11/08 04:49 PM CEST - @bitcoinzoli joined
11/08 04:4? PM CEST - @bitcoinzoli left
11/08 04:46 PM CEST - @bitcoinzoli joined
11/08 0?:?? PM CEST - @onnit777 left
11/08 03:29 PM CEST - @onnit777 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 | f/T 2 | reachable via |
|---|---|---|---|---|---|---|---|---|---|
| 1 | @anjanida | 11/13/22 | 2,898,263 | 29,879 | 97 | 109 | 8/9 | 7/8 | DBH- |
| 3 | @sodom-lv | 11/13/22 | 896,916 | 7,292 | 123 | 56 | 5/6 | 3/4 | --H- |
| 4 | @anjadani | 11/13/22 | 648,240 | 16,206 | 40 | 90 | 5/6 | 3/4 | ---F |
| 5 | @annijada | 11/13/22 | 64,890 | 1,545 | 42 | 26 | 4 | 6 | ---F |
| 7 | @ericohrn | 11/13/22 | 10,260 | 540 | 19 | 13 | - | - | ---- |
| 8 | @zenokrom | 11/13/22 | 8,460 | 423 | 20 | 16 | - | - | ---- |
| 9 | @zeeshannaqvi9th | 11/13/22 | 7,560 | 360 | 21 | 12 | - | - | DB-- |
| 11 | @xcryptogamer | 11/13/22 | 3,774 | 102 | 37 | 18 | 7 | 5 | ---- |
| 12 | @m0ssa99 | 11/13/22 | 3,600 | 150 | 24 | 14 | - | - | ---- |
| 13 | @felipek | 11/13/22 | 3,400 | 340 | 10 | 8 | - | - | ---- |
| 14 | @untzuntzuntz | 11/13/22 | 2,275 | 325 | 7 | - | - | - | ---- |
| 15 | @zeeshannaqvi7th | 11/13/22 | 1,350 | 270 | 5 | 4 | - | - | DB-- |
| - | @bitcoinzoli | 11/08/22 | 500 | 500 | - | - | - | - | ---- |
| 20 | @splinter2yop | 11/13/22 | 150 | 150 | 1 | 1 | - | - | ---- |
| 21 | @ OPEN | 11/13/22 | 0 | 0 | - | - | - | - | ---- |
@bitcoinzoli left
@ 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:
| Spot | Account | Calculated on | Score | DEC | Scrolls | Times brawled | Days ago | Tier 1 favorite | Tier 2 fav | reachable via |
|---|---|---|---|---|---|---|---|---|---|---|
| 6 | @ykyan2 | 11/13/22 | 64,704 | 674 | 96 | 50 | 8 | 1/2 | 7/8 | D--- |
| 16 | @ykyan4 | 11/13/22 | 1,254 | 38 | 33 | 19 | 8 | - | 3/4 | D--- |
| 17 | @mr-inc | 11/13/22 | 912 | 38 | 24 | 13 | 9 | - | - | ---- |
| 10 | @phantomx123 | 11/13/22 | 7,220 | 380 | 19 | 15 | 6 | - | - | ---- |
| 18 | @zekken555 | 11/13/22 | 240 | 60 | 4 | 3 | 10 | - | - | ---- |
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| 2 | @sm-rules | 11/13/22 | 1,561,705 | 18,373 | 85 | 110 | 12 | 13 | 15 | ---F |
| 19 | @shadowzekken | 11/13/22 | 180 | 60 | 3 | 1 | 12 | - | - | ---- |
Red card: Passive accounts with no DEC or Scroll contribution for more then two blawls, and therefore scheduled for removal, position by scrolls:
-- none
@ no one scheduled for removal for being passive
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.
Link to addendum
For our recent Member Management Notes Addendum with general guidelines and procedures see
@anjanida/member-management-addendum