!flagcape - Blacklist capes

[ZenithRogue]

Pretty simple !flagcape <username> adds cape to a blacklist

Could work as a toggle

[JackDotJS]

was thinking of having this as part of an all-in-one !blacklist command, something like

!blacklist <type> <value>

relevant: #111, #112

[ZenithRogue]

Here is the current list of blacklisted capes btw.

"capes": [
      "herobrine",
      "bishopfive",
      "god",
      "zbeub",
      "robot409",
      "xqcow",
      "felipe_neto_",
      "wilbursoot",
      "carpenter",
      "ZOOMERSLULW"
]

[ZenithRogue]

For the OBL rewrite, I check the name against the Mojang API, and record the UUID in the blacklist DB.

This is how each entry is stored. It is currently completely separate from the records.

{
      "moderator": 75123467123948,
      "user": "d6ebd3e3c0ef4e5a80db6ee537115a17",
      "when": 478567352
}

[JackDotJS]

This is what i was planning to do in NX. The bot already checks Mojang's API to fix case sensitivity, so UUID checks can be added with relative ease.

[LiamDun]

@ZenithRogue linked me this issue after messaging him to add a cape to the list so just thought I might list usernames that need to be added / removed

• remove god • remove bishopfive • remove robot409 • remove felipeneto • remove wilbursoot • remove carpenter • add BRCraftv • add GeePM • add hudzell • add jschlatt • add vinnyvinesauce

[ZenIsBestWolf]

This addition is confusing as most of the usernames don't have capes, only jschlatt and vinnyvinesauce, jschlatt's being disabled with a completely blank design, and vinnyvinesauce's being just a mushroom.

[LiamDun]

Are you sure? That's weird, well I didn't use namemc so we're probably getting different results

[ZenIsBestWolf]

I didn't either, I looked them up in the Cape Database. If they're not there, they shouldn't be anywhere else.

[LiamDun]

Huh that's super weird I used mcskinhistory so I could look up exactly what names have a certain cape design and I thought that was fine