I’ve done some work on this. Here’s what I’ve got so far. I’d like some feedback on both the framework - the change to rule 5.3 - and on the actual actions to undertake. Obviously, I need to fill out the actual values for voxel removal. At a guess, those values will be “1 minute,” “100 meters from the nearest grid,” and “0 meters from the nearest player,” but this needs some more testing first.
Thanks to @SurprisingEdge and @David_s for contributing input and reviewing the first drafts of this.
Create a framework for voting through actions. My hope is that we never vote through an action without discussing it first, but this gives us a way to propose one-shot obligations or deviations from Charter rules that don’t necessarily make sense in terms of Charter articles.
I believe the Power framework adequately resolves precedence between instructions (as defined below) and rules: the proposed changes to rule 2.4 clarify that, between instruments of a given power, articles come before other instruments, such as proposals. For example, an instruction to modify game data needs to have a power greater than that of Rule 9.2 (“The Official Server”) in order to override the obligation not to modify game data.
One ambiguity here that could probably use cleaning up is that an instruction can authorize (and require) an officer to break a standing rule, but can’t alleviate the standing rule entirely. I don’t think this will generally be an issue, but it might require some care in proposal-writing to ensure that officers aren’t left in a damned-either-way situation.
Use this framework to drastically shrink the Official Server’s data, so that connecting to it is not such an ordeal. Over the last few weeks we’ve been seeing increasing load times as players connect, and increasing disruption to existing connections caused by new players joining.
These appear to trace back to bloated voxel data, caused in large part by meteor impacts on the Earth-like planet. The data for that planet is now over 150 MB, whereas it’s under 1 kB on a new save, and @SurprisingEdge has observed that the data transmitted when he connects is approximately that size, leading to a multi-minute ordeal to join the server and a noticable increase in lag for other players.
By removing abandoned grids and all NPCs, this proposal ensures that as much of the voxel data is “smoothed” - restored to its original state and deleted from the game’s stored/transferred data - as possible. Testing suggests that this should reduce the 150 MB data to around 15 MB - still large, but only a tenth the size. Grids prevent the game from smoothing voxels in a large area around them even with the voxel cleanup settings tuned to be quite aggressive, as the game appears to use a grid-based system to determine what parts of a large voxel to clean up, rather than cleaning up on a point-by-point basis. Every stray grid appears to force a 2km by 2km area of the planet to remain in its eroded and dug-out state.
Title: Fine-Grit Sandpaper
Adoption Index: 4.0
Amend rule 2.4 (“Precedence Between Articles”) by changing its title to “Precedence Between Instruments”, and by replacing its text with the following:
In a conflict between instruments, the conflict shall be resolved as follows:
If the instruments in conflict have unequal power, the instrument with the highest power takes precedence;
Otherwise, if both instruments are articles of this Charter, the article appearing earliest in the Charter takes predecence;
Otherwise, if either instrument is an article of this Charter, that instrument takes precedence;
Otherwise, the instrument adopted first takes precedence.
No change to this Charter can occur that would cause an article to directly claim precedence over this rule as a means of determining precedence. This rule takes precedence over any article that would permit such a change to this Charter.
Amend rule 5.3 (“Official Duties”) by appending the following paragraph:
Where permitted by this Charter, an instrument can, as part of its effect, instruct an officer to take action. The officer must perform the action in a timely fashion, once and only once per instruction, in the order the instructions appear in the instrument. The officer should publicly announce that the instructions have been completed after taking action.
Instruct the Space Master to create a backup of the game data.
Instruct the Space Master to remove the following categories of grids from the game:
- Grids belonging to players who have not logged in in two or more weeks,
- Grids more than 45,000 km from the Earth-like planet,
- All grids belonging to NPCs which are further than 100m from a player-owned grid, and
- Grids which, at the Space Master’s discretion, appear to be abandoned debris on the surface of any planet.
Instruct the Space Master to smooth the game’s voxels, by the following procedure:
- Configure the trash removal settings as follows:
TODO (needs research)
Observe an unoccupied area until the game removes voxel modifications, and
Restore the trash removal settings to their original values.
Instruct the Space Master to restore the backup of the game data if, on inspection of least two asteroid or planetary static grids, any grid appears to have been rendered inaccessible or unusuable due to restored voxel material.