search

JackDotJS / OptiBot

(DISCONTINUED) The original Discord bot for OptiFine. https://discord.gg/3mMpcwW
1 stars 0 forks source link

!cape - Specify between non-existent capes and disabled capes #262

Closed JackDotJS closed 3 years ago

JackDotJS commented 3 years ago

OptiFine's cape server has a separate route for finding disabled capes in a similar manner to regular capes.

http://s.optifine.net/capes/inactive/<USERNAME>.png

This means disabled capes can still be viewed, but this could potentially become a sort of privacy concern. Would it be useful for OptiBot to state that a given user's cape is currently disabled, or should it simply assume they do not have a cape as it currently does?

ZenIsBestWolf commented 3 years ago

Continuing to assume the user does not have a cape is the way to go IMO, because most people don't know there is an inactive path, and some users may have inactive capes they find offensive or no longer agree with, and just didn't think to change it.

JackDotJS commented 3 years ago

realized pretty soon after posting this i worded that last part pretty badly.

to clarify, there are a few options when the users cape cant be found in the normal route:

  1. assume there is no cape at all. (this is what is currently done)
  2. check for disabled cape, show it as normal. (probably worst idea)
  3. check for disabled cape, simply return a message saying its disabled.
ZenIsBestWolf commented 3 years ago

still gonna go with 1 because then that prompts the user to ask someone else "hey can i see the disabled cape" or something along the lines, but its much better than number 2, i suppose it wouldnt be too much of a difference.

JackDotJS commented 3 years ago

gonna close this. indirectly telling users that there's a way to tell if a cape is disabled or not will likely prompt them to find out how to view them. this is not public knowledge as far as im aware, and i'd imagine sp would like to keep it that way.