Cycle 13/Ruleset Draft - Revision history

RandomNetCat: 60 revisions imported: Import Miraheze archive 2022-10-29

2022-11-25T02:08:00Z

60 revisions imported: Import Miraheze archive 2022-10-29

← Older revision	Revision as of 02:08, 25 November 2022
(No difference)

miraheze>Veganzombeh: wait I meant to change it to this

2022-10-09T23:29:35Z

wait I meant to change it to this

← Older revision		Revision as of 23:29, 9 October 2022
Line 6:		Line 6:
	All times mentioned in the rules are in UTC. Days begin at 00:00 UTC. Weeks begin on Sunday. Each phase is either (Sunday, Monday, and Tuesday), (Wednesday and Thursday), or (Friday and Saturday).		All times mentioned in the rules are in UTC. Days begin at 00:00 UTC. Weeks begin on Sunday. Each phase is either (Sunday, Monday, and Tuesday), (Wednesday and Thursday), or (Friday and Saturday).

	The first Phase ~~starts as soon as~~ the ~~Cycle~~ begins and anything that would have taken place at the start of the first Phase take place at the start of the Cycle.		The first Phase is ongoing when the cycle begins and anything that would have taken place at the start of the first Phase take place at the start of the Cycle.

	Phases are identified by successive Roman numerals; the first phase of the cycle is Phase I.		Phases are identified by successive Roman numerals; the first phase of the cycle is Phase I.

miraheze>Veganzombeh: lets not delay the start week

2022-10-09T23:28:19Z

lets not delay the start week

← Older revision		Revision as of 23:28, 9 October 2022
Line 6:		Line 6:
	All times mentioned in the rules are in UTC. Days begin at 00:00 UTC. Weeks begin on Sunday. Each phase is either (Sunday, Monday, and Tuesday), (Wednesday and Thursday), or (Friday and Saturday).		All times mentioned in the rules are in UTC. Days begin at 00:00 UTC. Weeks begin on Sunday. Each phase is either (Sunday, Monday, and Tuesday), (Wednesday and Thursday), or (Friday and Saturday).

	The first Phase starts at the ~~beginning~~ of the first ~~full Sunday after~~ the Cycle ~~begins~~.		The first Phase starts as soon as the Cycle begins and anything that would have taken place at the start of the first Phase take place at the start of the Cycle.

	Phases are identified by successive Roman numerals; the first phase of the cycle is Phase I.		Phases are identified by successive Roman numerals; the first phase of the cycle is Phase I.

miraheze>Logistic-bot: Make goal list a bullet list

2022-10-07T08:11:17Z

Make goal list a bullet list

← Older revision		Revision as of 08:11, 7 October 2022
Line 52:		Line 52:

	=== Goal list ===		=== Goal list ===
	Have the most Coins at the end of the Loop.
			* Have the most Coins at the end of the Loop.

	=== Reward list ===		=== Reward list ===

miraheze>CodeTriangle: /* Items */ import trades

2022-10-06T01:23:40Z

Items: import trades

← Older revision		Revision as of 01:23, 6 October 2022
Line 63:		Line 63:

	For an entity to lose an item is for that item to be destroyed from that entity's possession. To revoke an item from an entity is to destroy it from that entity's possession.		For an entity to lose an item is for that item to be destroyed from that entity's possession. To revoke an item from an entity is to destroy it from that entity's possession.

			A trade is an exchange or transfer of items between two entities, with each entity giving a specified finite set of items to the other. Reputable players may trade items with other reputable players. A trade between two players takes place when both players explicitly consent to the trade in #trades within 7 days of each other.

	== Orbs ==		== Orbs ==

miraheze>Randomnetcat: Make tracking fully non-binding

2022-10-06T01:20:05Z

Make tracking fully non-binding

← Older revision		Revision as of 01:20, 6 October 2022
Line 20:		Line 20:
	A players is "reputable" if they have continuously been a player for the previous seven days or if they have continuously been a player from a time that was within 3 days of the round starting.		A players is "reputable" if they have continuously been a player for the previous seven days or if they have continuously been a player from a time that was within 3 days of the round starting.

	Whenever a player performs an action that would modify the ~~gamestate,~~ the ~~result of that action must~~ be ~~"claimed" before it is considered valid. To claim the outcome of a valid action~~, a reasonable effort ~~must be made~~ to track the outcome of the action in the generally-agreed-upon applicable location. Players should take responsibility by making their own claims on their actions, but a claim for a player's action can be made by any reasonable party (such as other players) that is capable of tracking gamestate modifications.		Whenever a player performs an action that would modify the information that the players generally agree should be tracked, that player should make a reasonable effort to track the outcome of the action in the generally-agreed-upon applicable location.

	== Generate Coins ==		== Generate Coins ==

miraheze>Randomnetcat: Remove auto-invalidation provision

2022-10-06T01:16:44Z

Remove auto-invalidation provision

← Older revision		Revision as of 01:16, 6 October 2022
Line 21:		Line 21:

	Whenever a player performs an action that would modify the gamestate, the result of that action must be "claimed" before it is considered valid. To claim the outcome of a valid action, a reasonable effort must be made to track the outcome of the action in the generally-agreed-upon applicable location. Players should take responsibility by making their own claims on their actions, but a claim for a player's action can be made by any reasonable party (such as other players) that is capable of tracking gamestate modifications.		Whenever a player performs an action that would modify the gamestate, the result of that action must be "claimed" before it is considered valid. To claim the outcome of a valid action, a reasonable effort must be made to track the outcome of the action in the generally-agreed-upon applicable location. Players should take responsibility by making their own claims on their actions, but a claim for a player's action can be made by any reasonable party (such as other players) that is capable of tracking gamestate modifications.

	~~If the outcome of an action taken by a player is not claimed within 24 hours after the phase in which the outcome would take place, the action is invalidated.~~

	== Generate Coins ==		== Generate Coins ==

miraheze>Randomnetcat: Add reputability and claiming

2022-10-06T01:13:47Z

Add reputability and claiming

← Older revision		Revision as of 01:13, 6 October 2022
Line 17:		Line 17:

	Actions that are to be performed by sending a message are done by sending a message in the appropriate channel that clearly and unambiguously sets forth intent for the action to be taken.		Actions that are to be performed by sending a message are done by sending a message in the appropriate channel that clearly and unambiguously sets forth intent for the action to be taken.

			A players is "reputable" if they have continuously been a player for the previous seven days or if they have continuously been a player from a time that was within 3 days of the round starting.

			Whenever a player performs an action that would modify the gamestate, the result of that action must be "claimed" before it is considered valid. To claim the outcome of a valid action, a reasonable effort must be made to track the outcome of the action in the generally-agreed-upon applicable location. Players should take responsibility by making their own claims on their actions, but a claim for a player's action can be made by any reasonable party (such as other players) that is capable of tracking gamestate modifications.

			If the outcome of an action taken by a player is not claimed within 24 hours after the phase in which the outcome would take place, the action is invalidated.

	== Generate Coins ==		== Generate Coins ==

miraheze>CodeTriangle: /* Items */ import item actions

2022-10-06T01:09:45Z

Items: import item actions

← Older revision		Revision as of 01:09, 6 October 2022
Line 54:		Line 54:

	== Items ==		== Items ==
	Items are entities ~~that players can have in their inventory~~. Items are to be ~~tracked publicly (preferably~~ by the owner~~) when created, obtained, transferred, received~~, destroyed... ~~etc~~.		Items are entities described as such by the rules. Items are always owned by exactly one entity, and they cannot be owned by any entity that the rules do not allow to own that item. By default, only players may own items. When an item's owner cannot reasonably be determined using publicly available information, it is instead destroyed.

			For an entity to gain an item is for that item to be created in that entity's possession. To grant an entity an item is to create it in that entity's possession.

			For an entity to lose an item is for that item to be destroyed from that entity's possession. To revoke an item from an entity is to destroy it from that entity's possession.

	== Orbs ==		== Orbs ==

miraheze>Randomnetcat: Rewrite reward/goal selection and a

2022-10-06T01:08:36Z

Rewrite reward/goal selection and a

← Older revision		Revision as of 01:08, 6 October 2022
Line 43:		Line 43:

	==Leaderboards ==		==Leaderboards ==
	At the ~~beginning of every Loop~~, 1 goal ~~is randomly selected~~. ~~Each Goal is~~ randomly ~~given a~~ reward ~~from~~ the ~~list of rewards~~.		Each loop has at most one active goal. If the current loop does not have a goal, any player can randomly select one goal to become active in #game-actions; the selection becomes the loop's active goal. For each loop, each active goal has at most one reward. For any active goal in the current loop without a reward, any player can randomly select one reward for that goal in #game-actions; that reward becomes the goal's reward for this loop.

	At the ~~end~~ of a loop, the players that best accomplished ~~a Goal that was selected at~~ the ~~beginning of that Loop get~~ the reward ~~selected~~ for that ~~Goal~~, ~~receiving this reward when the next loop begins~~.		At the start of a loop, the players that best accomplished each active goal in the previous loop, if any, gain the reward for that goal in that loop, if any.

	=== Goal list ===		=== Goal list ===