Added messages for council-rules

messages/council_rules/1.txt

@@ -0,0 +1,2 @@
+**Council Rules**
+The following are the council rules.

messages/council_rules/2.txt

@@ -0,0 +1,9 @@
+**Emeritus**
+1. The clan chat rank for Emeritus is General :Rank_General: and unaffected against inactivity demotions.
+2. Emeritus is, who...
+2.1 founded Dakiny.
+2.2 was elected as Clan Leader and was active as Clan Leader for at least one entire quarter.
+2.3 was nominated and successfully elected in an Emeritus poll.
+2.4 donated more than 200m to the RS3 clan funds (multiple transactions will be added together).
+2.5 has recruited more than 40 members to the clan.
+2.6 served as admin for 2 years or longer.

messages/council_rules/3.txt

@@ -0,0 +1,8 @@
+> __**Clan Member Management**__
+
+*Refer to <#667091901551345684> for how promotions / demotions are generally ruled*.
+
+**#1** Any star-related rank change (Lieutenants <:Rank_Lieutenant:479008102478512128>, Captains <:Rank_Captain:479008128893976576>, Generals <:Rank_General:479008158027874315>) **must** be voted on via a poll in <#666645356838125607>.
+**#2** "Banana" ranks (Recruit <:Rank_Recruit:479007976200601604>, Corporal <:Rank_Corporal:479008028880928768>, Sergeant <:Rank_Sergeant:479008059083980811>) are managed without specific communication, but must follow the rules listed in <#667091901551345684>.
+**#3** Possible future Daks (recruits) must have passed a guesting trial of 7 days and attended to at least 1 clan event before being invited to Dakiny.
+**#4** Any new guests, or member invitations must be posted in <#666426416337911818> so we may maintain our member spreadsheet.

messages/council_rules/4.txt

@@ -0,0 +1,16 @@
+> __**Server management rules**__
+
+**#1** Channels must not be deleted and should be archived.
+**#2** When archiving a channel, use the *Hidden categories* and archive according to the description. For example, an old event channel should be archived in *Hidden | Events archives* category.
+**#3** If a public channel hasn't been used for over a month, it can be marked with the following message and then archived. 
+
+> ⚠️ This channel was marked for deletion ⚠️ 
+> If you want to save this channel, speak now and help keep it alive.
+> If no one says anything, this channel will be deleted in 7 days. Salvage any pictures or information you want before then.
+
+**#4** If the clan council decides to archive any of its own channels, then no message or announce needs to be made. 
+**#5** `Hidden | Council archives` has sensitive information in past discussions from council terms and should only be viewed by current clan council members.
+**#6** `Hidden | OSRS channels` has sensitive information as past discussions from the OSRS council and should only be viewed by current clan council members.
+**#7** Other categories can be open to view for the public and any channel can be unarchived if the Clan Council deems that necessary.
+**#8** Everyone's name in the server must be their in-game name. In case of having multiple, use | to give them both names. For example *Dak Name | Iron Name*.
+**#9** Changes to the server structure can be done, but they must pass Clan Council vote. Overhauls must the thoroughly discussed to avoid changing the server every new term.

messages/council_rules/5.txt

@@ -0,0 +1,9 @@
+**#10** The <@&810567528228061236> role (grants access to event_participation) is a temporary role granted for someone when they host a clan event, but needs to be taken away if they haven't hosted an event in the past 2 months.
+**#11** Server owner must create and manage the voting channel for the next term following the dates expressed in <#668483654694993928> and the sub rules bellow.
+**#12** Roles that members get as a reward from clan events are always temporary rewards to avoid having too many roles in the server that have 1-2 people and no purpose.
+**#13** All bots in the Dakiny server are of one of the following categories and bots that don't fall into those categories cannot be added to the server:
+**a.** Runescape (RS3 and/or OSRS and any new game under the Runescape umbrella) related bots such as RuneInfo, SuityBot and Friendliness.net.
+**b.** Music related bots such as FreddyBoat and Rythm.
+**c.** Management related bots such as Carl bot and Ticket Bot.
+ **#13.1** Examples of bots that are not allowed in the server as they don't fit the theme (runescape) and would clutter the server, such as Tamamo bot, Meme bots, gif generation bots, Purplebot (or any other private bots made by clan members), Pokemon bots, other games related bots, etc.
+**#14.** DO NOT modify permissions on <#802355370260693013>, unless it’s to add/remove persons as voted on. It is intentionally not synced with the Clan Council category.

messages/council_rules/6.txt

@@ -0,0 +1,12 @@
+__**Sub rules for voting management**__
+ **11.1** Use the main text from previous vote channel with minor changes if necessary and post it, preferably 3+ days before start of the candidacy timeframe, with the channel to read only.
+**11.2** When the candidacy timeframe starts, open the channel to write, and, if necessary, do a ghost ping @ everyone. 
+**11.3** Make sure all candidates have meet the requirements to be candidate. If needed check with the council about it. Council may vote to allow someone that have outgrown their warning or redeemed themselves to run. 
+**11.4** When the voting timeframe starts, close the voting channel for writing and make sure the option to add reactions is open. Add an <:Rank_Admin:479008185240518656> to each candidate as a place holder.
+**11.5** Keep an eye on the votes and message clan members that voted twice. Before voting is done, take your <:Rank_Admin:479008185240518656> down and vote yourself.
+**11.6** Once voting is done, announce the new council in the voting channel.
+ **11.7** Give everyone that won the election the role <@&494624264805285889> and tell them to read: <#668085252744282112> and <#668132551059177492>. 
+ **11.8** Close the voting channel for those only and start the <@&478315397033099264>  candidacy and voting.Once those are done, announce the new council in <#642729302630072320>.
+ **11.9** Once finished, close the channel for <@&500877978784497684> and <@&478315397033099264> only and archieve it in the HIDDEN | VOTING ARCHIVES category.
+ **11.10** When the term ends, before giving out the server ownership, give the <@&494624264805285889> their <@&500877978784497684> roles and take the <@&500877978784497684> roles from the ones that won't be part of the council anymore.
+**11.11** Those running for High Council roles must have previously held a seat in Council within the last 12 months, else they are not eligible.

messages/council_rules/7.txt

@@ -0,0 +1,11 @@
+**__OSRS clan leadership rules__**
+**#1** The "Dakiny" OSRS clan exists as a place holder to keep the name within our control and avoid having a second clan with our name but different rules and mindset as ours.
+**#2** The  "Dakiny" OSRS clan leadership should be passed down to a clan council member that isn't RS3 Clan Leader or Discord Leader.
+**#3** To hold the "Dakiny" OSRS clan leadership, said clan council member have to:
+- have been a council member for at least one term prior to the current one;
+- have an OSRS account with authenticator and bank pin;
+- have played at least 25 hours in said account (Jagex's requirement to be a clan leader in OSRS).
+**#4** Rule of exceptions: 
+- In the case of a term which no clan council member meet the requirements in rules **#2** and **#3** simultaneously, then the Discord Leader can hold the OSRS clan leadership as an exception.  
+- If the Discord Leader also can't hold it, then the RS3 Clan Leader can hold the OSRS clan leadership as an exception.
+- If no one in the Clan Council meet the requirements to hold the OSRS clan leadership, then the Clan Council can vote for one of the member of the <@&268011909427494913> or <@&315481884681568256> hold it for that term.

messages/council_rules/8.txt

@@ -0,0 +1,3 @@
+**#5** To pass the ownership, promote the next owner to deputy owner, let them login/relog after that. Select the option to resign, making sure the name of the new owner display in the interface is the correct player. Like in the following example:
+https://cdn.discordapp.com/attachments/668132551059177492/901926232676008046/unknown.png?ex=6645c002&is=66446e82&hm=26bae626168cba13efc6f073f962fa2c57fee29772ec5a0bcd1595eb851a894b&
+The process takes 7 days to officially pass the ownership over.

messages/council_rules/9.txt

@@ -0,0 +1,7 @@
+> Template message for Emeritus <#642729302630072320> (Can be changed if needed)
+
+Every quarter Dakiny's Clan Council can nominate and vote in members of our community that have gone above and beyond traditional expectations contributing enough to the clan to have an enduring positive impact on our clan.
+
+Those that win this nomination receive the role of Emeritus, which grants them a permanent minimum rank in our clan and a fancy role in discord. 
+
+For this last quarter, the Dakiny Clan Council nominated and voted on **<tags here>** to receive this honor. Congratulations!