1 - Developer can disabled tchat tools in settings

[YglesEyes]

Add in settings

{
  "public": {
    "disabledFeatures": ["textualCommunicationTools"]
  }
}

[ramnes]

139 architecture doesn't work for what you want to achieve? We could extend it with a dropdown for all textual communications tools.

[YglesEyes]

The goal is to have a more global restriction for the server and not only for a team, for the moment it seems easier to use flag instead of rework the code to have optional modules.

[ramnes]

Okay, then we probably want to streamline the way these permissions work because it seems to me that it's going all over the place.

I would suggest a common list of modules across the different types of feature flag systems and a generic way of toggling these modules at each level (guests / level / server), with a config that would look like this (or anything really):

{
  "features": {
    "useMessaging": {
      "enabled": true,
      "guestEnabled": false,
      "levelConfigurable": true
    },
    ...
  }
}

What do you think?

[ramnes]

At the very least we should use the same format and module names, i.e. here we should replicate how guests is structured:

{
  "features": {
    "useMessaging": false
  }
}

rather than

{
  "disabledFeatures": ["textualCommunicationTools"]
}

or it will be a nightmare to streamline later. :(

[YglesEyes]

Like it, it is more generic and configurable, i don't have time yet but I will implement it ASAP