by Max Barry

Latest Forum Topics

Advertisement

3

DispatchMetaReference

by The Dichromatic Mechanism of August. . 130 reads.

NS Leaders Staff Reference

How the bot works

When a new user enters the server for the first time...

  • The bot greets them in DMs and asks for their founder or delegate nation.

  • If their nation has not been verified previously, the bot has them verify it. This process is identical to NSV in other servers.

  • The bot checks if that nation is a founder, delegate, or senior delegate in its current region.

  • If it is, the bot assigns the proper roles and lets the user into the server with a public greeting.

  • If it is not, the bot asks for the region where the nation is eligible, and repeats the previous two steps.

  • If the user fails to ever provide an eligible nation, they are confined to the lobby channel and will be kicked after three days.

When a returning user enters the server...

  • The bot checks if they are still a founder, delegate, or senior delegate somewhere, and if they have disassociated themselves from their eligible region(s).

  • If they are still eligible, the bot lets them into the server with a public greeting.

  • If they are not, the bot asks them to verify a founder or delegate nation.

  • If the user does not have an eligible nation and fails to ever provide one, they are confined to the lobby channel and will be kicked after three days.

When a user types the command >nsl scan...

  • If the provided nation has not been verified, the bot has them verify it.

  • The bot scans the nation's current region's history for eligibility.

  • If the nation is eligible in that region and the user has not disassociated themselves from that region, the bot updates the user's roles accordingly.

  • If the nation is not eligible in that region, the bot asks for the region where the nation is eligible, and repeats the previous two steps.

When a user types the command >nsl disassociate...

  • If the user has nations with eligibility in that region, or if they verify such nations in the future, they lose that eligibility. This is mostly useful if the user has a role for a puppet storage or other insignificant region because of a nation they verified elsewhere.

  • To restore their eligibility (or potential future eligibility) in that region, the user can type the same command again.

When a staff member types the command >nsl add_senior...

  • The user gains former senior founder or delegate status in the specified region with the specified nation.

  • For former senior founders, this is useful if the region has been refounded (erasing the record of their foundership), or if it is common knowledge that the region had at least fifty WA members during the user's foundership, but not during a time when the founder nation was verified by the user.

  • For former senior delegates, this is useful if the region has been refounded (erasing the record of their delegate term), if their delegate term was prior to March 2016 (when the site began tracking endorsement history), or if their delegate term was prior to 2010 (when the site began tracking regional history).

When a staff member types the command >nsv_exempt...

  • That user will no longer receive role adjustments during the daily update, and they will not be automatically kicked if they are not eligible to remain.

  • To remove their exemption, a staff member can type the same command again.

When a staff member adds a user to the Watchlist...

  • If that user is in a server that uses AugustinAndroid v2 and has the Watchlist feature enabled, the bot sends a warning to the server's staff. That warning includes a description and evidence of the person's activities. If the user is a spambot, the bot automatically bans it instead of sending a warning.

  • In the future, whenever that user enters a server that uses AugustinAndroid v2 and has the Watchlist feature enabled, the bot sends a warning to the server's staff (if it is a person) or automatically bans it (if it is a spambot).

Daily update...

  • Verified nations that have become founders, delegates, senior founders, or senior delegates in the last day are updated with their new status.

  • Each user who is eligible but did not have the proper regional or status roles gains them.

  • Users who have become ineligible lose all their roles and gain the Pending role, which confines them to the lobby channel.

  • Pending users receive a private message advising them to verify an eligible nation.

  • Users who have been Pending for three days are kicked.

  • Regional roles that do not belong to any members are deleted.

Recruitment...

  • On a regular basis throughout the day, the bot automatically checks for new founders and delegates across the world.

  • Nations meeting certain criteria receive a personal invitation to the server.

Weekly questions...

  • Every Saturday at noon, Eastern US time, the bot automatically posts a discussion question in #ns_leadership and pings everyone.

  • These questions come from a pre-written list. When all the questions have been used, the bot will notify the server staff.

  • Staff members can add new questions to the list using the command >nsl add_question, view the list using the command >nsl list_questions, disable the questions using the command >nsl questions stop, or re-enable the questions using the command >nsl questions start.

Regional role colors...

  • When a new regional role is created, the bot detects the most frequent color on the region's flag and sets it as the role's color. Roles for regions without flags are set to the default transparent gray.

  • The current founder and current delegate of a region can use the command >nsl edit_color to change their regional role color. Server staff can change any regional role color in this way.

  • Server staff roles are set to the default transparent gray so staff members' regional colors remain visible.

  • Staff members should usually avoid re-ordering regional roles, but if everyone holding two regional roles is in agreement, those two roles may be re-ordered for the purpose of changing the visible role color.

How the roles and permissions work

  • #lobby is only visible to Pending users and server staff. Pending users cannot view any other channels, and they cannot upload files.

  • #info and #announcements are visible to all eligible users. All server staff may post announcements in #announcements.

  • #console is visible to all server staff only, and is meant for all bot logging and administrative discussion.

  • #ns_leadership, #hangout, #bot_commands, and general-VC are visible to all eligible users. All eligible users have at least one of the roles Senior, Founder, and Delegate, so all three of those should have the Read Messages permission in general-access channels.

  • #region_planning and #wa_discussion are founder-only and delegate-only, respectively. The Senior role does not have access to either channel because it includes both founders and delegates. Instead, Ex-Founders and Ex-Delegates should have access to each channel, respectively.

  • #watchlist is visible to all eligible users, but only server staff, current founders, and current delegates can post. The Send Messages permission is not denied to the Senior role because that role includes current founders and current delegates. Instead, Send Messages is denied to Ex-Founders and Ex-Delegates.

  • #senior_lounge is only visible to Seniors and server staff. Seniors have no other special permissions.

  • The NS Founders archives still exist, but are only visible to administrators.

Expectations for moderators

  • Enforce channel topics.

  • Pin and delete posts. Spam should be deleted. Pins are at your discretion.

  • Warn and mute users in the event of repeated spam.

  • Kick/ban users. Please use this sparingly. NSFW avatars are grounds for banning.

  • Operate the #watchlist system.

  • Assist players who are having difficulty with verification or scanning.

Dos and Do Nots

  • You can add new channels, or new overwrites to existing channels. If you make a new channel, deny the Manage Permissions and Read Messages permissions to @everyone in that channel. The roles Senior, Founder, and Delegate do not necessarily overlap, so if you want everyone to see the channel, all three of those roles need the Read Messages permission.

  • You can delete or rename regional roles, but those changes will be auto-reverted at the next update.

  • You can manually remove the Pending role. If the user does not have a verified founder/delegate nation at the next update, the Pending role will be restored to them, and they will be kicked within three days of entering the server unless they confirm their eligibility with the bot.

  • You can adjust the NSV settings through the settings menu, but they have been disconnected and any changes will have no effect.

  • Do not rename or delete any of the following roles: "Server Bot", "Administrator", "Moderator", "Senior", "Ex-Founder", "Ex-Delegate", "Founder", "Delegate", "Pending", and "Conference Attendee." Those are all the non-regional roles.

  • Do not change the existing channel permission overwrites.

RawReport