Jump to content

Organization management & Exceptional NQ Interventions


Recommended Posts

Hi everyone.

 

Until now, we couldn’t manually manage (remove/promote) Legates in an organization easily on the administration side.

Since Yesterday, we are able to use a feature simplifying considerably the process. 

 

As we already mentioned many times in the past, we (Novaquark) don’t want to involve ourselves in the management of organizations created by players. However, we are also aware that the current (and temporary) state of the management system contains obvious flaws. You know it. We know it. As this is still “work in progress”, we hoped that organizations creators will be reasonable enough to avoid abusing the well-known flaws of the system and would wait that all the rules are implemented before trying to sabotage other organizations. 

 

So we are going to state the obvious here:
It’s ok to “play a bad guy” and use dirty tricks once all the rules are implemented. However, it’s absolutely not ok to start exploiting the flaws of a work in progress system: this is not “playing a bad guy”, this is just toxic behavior and trying to gain an advantage while not playing by the rules.

 

That’s why - despite our will of non-involvement - we will make exceptions until the full implementation of the RDMS (Rights & Duties Management System) for the Organizations.

 

Why did we decide to intervene? 

Two reasons:

1) In the current state, a Legate has much more power than in the final system, due to the minimalistic mechanisms temporarily in place. If in the current system, any Legate has the right to promote a member to Legate status by himself alone, in the final system the default rights will be completely different: promoting a legate will be done only with a vote by majority rule, or the right to promote someone will be given to specific persons and not every Legate.

2) In the current state, a Legate cannot be demoted by any mean (even by the creator of an organization). In the final system, default configurations will allow to demote a Legate with a vote by majority rule. A Legate could also be demoted by specific persons who have been given the right (most probably by the Organization founder) to do so.

 

How is this going to work?

Each organization is going to have one "wild card": if there is a problem with the Legates in an Organization, you can contact the support team at support@novaquark. However, keep in mind we (Novaquark) reserve the right to intervene (or not) on a case by case basis. 

 

Example of a case where we will intervene:
Some Legate using the flaw of the current temporary system to vandalize (or generate troubles in) an organization.

 

Example of a case where we won’t intervene:
Two organizations have merged in one, and now both creators of previous organizations want to mutually exclude each other from the organization. In this kind of case, we won’t remove anyone. We won’t favorize one creator above another. However, we will do our best to help finding a satisfying solution for both parties.

 

As a global reminder:
If someone finds a loophole in the rules in place (that may happen), and this loophole is used to generate trouble and spread a toxic behavior, we won’t stay idle watching the situation deteriorating. 

 

Best Regards,
Nyzaltar.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...