Documentation
Table of Contents
Website
This website serves two main purposes:
- To be a repository of all information related to this season of Nomic.
- To interact with the automation system (Nomic Bot).
Nomic Bot
The Nomic Bot Discord bot is used to manage the NAS from the Nomic Discord server, or through Discord direct messages.
Commands
Nomic Bot commands can be executed through global/guild-specific slash commands, or by prepending the command prefix $
to the command and space-delimited arguments.
-
help
Send a list of commands to control Nomic Bot
-
ping
Test to see if Nomic Bot is online, and get ping time in ms
-
players
Get a list of players in the turn order
-
votes [message ID]
Get the votes on a proposition
To get the ID of a message, ensure "Developer Mode" is on in Discord's Advanced Settings, right-click the message, and select "Copy ID".
-
rand [lower bound] [upper bound]
Generate a random integer between the lower and upper bounds (inclusive).
If no bounds are given, this command returns a random number between 0 (inclusive) and 1 (exclusive).
-
roll [XdY]
Roll X dice of size Y.
-
listrand [list]
Randomise a given space-/comma-separated list.
-
randplayer
Return a random player.
-
randplayerlist
Return the list of players in a random order.
Propositions
All in-game propositions should be made in the #propositions channel on the Nomic Discord guild.
Syntax
When making a proposition, it is always best to use a syntax the same as, or similar to, that of the other players.This is mostly for clarity and human-readability, though in the future the automation system will attempt to automatically parse your propositions, and if they use invalid syntax that may cause issues.
If you don't like the syntax that other players are using, you can modify it (within reason) to suit your needs, but if you do, ensure that you remain consistent for the rest of the game.
So with that said, it is preferable that you use recent propositions as a reference on how to format your proposition. If you need any more clarity, see below:
The following is the official template you should use to format your propositions:
**[Modification Type]**
> [Path] - [Title]
[Content]
**[Modification Type]**
> [Path] - [Title]
[Content]
[Repeat as necessary]
> [Path] - [Title]
[Content]
**[Modification Type]**
> [Path] - [Title]
[Content]
[Repeat as necessary]
[Modification Type] = The type of modification being made to the rule tree.
Options include:
-
Addition
Add a new rule to the rule tree.
This requires a path and a title. Content is optional.
-
Content Edit
Replace the content of a rule.
This requires a path and the complete new rule content.
-
Path Edit
Moves a rule on the rule tree (changes its path).
This requires the original path and the new path.
-
Title Edit
Change the title of a rule.
This requires a path and the new title of the rule.
If using a title path, the recommended structure is:
**Title Edit**
> [Path]
[New Title]
If using an ID path, the recommended structure is:
**Title Edit**
> [Path] - [New Title]
-
Deletion
Delete a rule.
This requires a path.
-
Content Appendication
Append more content to the end of a rule.
This requires a path and the content to append.
-
Transmutation
Transmute a rule.
This requires a path.
-
Miscellaneous Change
Make a change to the game which has no dedicated modification type.
This requires a description of the modification to be made to the game.
[Path] = The "path" (location on the rule tree) of the rule you are adding/modifying/removing.
There are 2 accepted ways to format the path:
-
Title Path
A string of rule titles going down the tree, joined by ">".
Example: Propositions > Paths > Title Path -
ID Path
A string of rule "relative IDs" going down the tree.
Example: 3.3.1
[Title] = The title of the rule you are adding/modifying/removing.
If you use a Title Path to refer to your rule, the title of the rule should be included as part of the path, so including the title separately is redundant and should be avoided to prevent confusion.
If you use the ID Path, although not strictly necessary in modifications, it is highly recommended that you include the title of the rule. If it is an addition, a title is always necessary.
[Content] = The functional part of your rule.
For most purposes, this is the only part of your proposition that really matters.
The content of a rule needs to be easily understandable and entirely objective. Anything up to interpretation can (and will) cause loopholes or other issues, so ensure that you check your wording (and spelling) to prevent those issues from ever appearing.
The following is a portion of an exemplar proposition (link) made using all recommended syntax:
Content Edit
4.2 - Suggestion Voting
After the Judge has made a suggestion, all players may vote (up or down) on it. If an upvote majority is reached within 72 hours, the suggestion is adopted. Otherwise, the Judge's suggestion is rejected and a new Judge is chosen to make a new suggestion.
Addition
4.4 - Time Limit
If a Judge does not suggest a fix to the issue within 48 hours, a new Judge is chosen to make a suggestion.
Title Edit
6 - Miscellaneous
Addition
6.2 - Periods
Every week (commencing on Sunday 00:00 UTC) is divided into a 72 hour period, followed by a 96 hour period.
Title Edit
7.1.1 - Aquisition
4.2 - Suggestion Voting
After the Judge has made a suggestion, all players may vote (up or down) on it. If an upvote majority is reached within 72 hours, the suggestion is adopted. Otherwise, the Judge's suggestion is rejected and a new Judge is chosen to make a new suggestion.
Addition
4.4 - Time Limit
If a Judge does not suggest a fix to the issue within 48 hours, a new Judge is chosen to make a suggestion.
Title Edit
6 - Miscellaneous
Addition
6.2 - Periods
Every week (commencing on Sunday 00:00 UTC) is divided into a 72 hour period, followed by a 96 hour period.
Title Edit
7.1.1 - Aquisition