Pocket Configurator
The Pocket configurator tool can be brought up any time from the terminal by running configure on a Pocket computer after installing the pocket application. It will automatically come up on application startup if there is no valid configuration present, as shown in the first screenshot below.
General Tips:
- You can paste values into number/text fields
- You can navigate around with
tabandshift+tab(and arrow keys where applicable) - You can
ctrl+aor double click number/text fields to select all - When configuring the system, fields will be pre-filled with any valid existing configuration data
- You will be shown a summary of settings before any are saved
Below are two examples of the main menu. If the configurator is started by the Pocket app itself due to a lack of a valid configuration, the red warning text in the first example will be present. If any previous configuration is present, the view option will be enabled.
There is an embedded configuration file change log that will show what fields have been changed, added, or removed. This will help you figure out why a previously valid configuration may no longer be valid.
This option shows the currently active configuration of the device. Facility authentication keys will be censored via asterisks, but can be shown via the unhide button.
This option will walk you through configuring the Pocket computer. Fields will be pre-filled with existing configuration data if present, otherwise the defaults will be shown.
On these pages, you can choose between various UI format preferences. You can customize the temperature and energy scales and the color of plutonium and polonium pellet representations. The pellet colors changed after Mekanism 10.4+, so the waste coloring can be selected to match that.
You will first need to provide channel information. These are the channels you have chosen per this page, or they may be the defaults. Defaults are perfectly fine on single player, though not recommended on multiplayer if any other people may be using this project.
Next, continuing network configuration, there is the connection timeout that decides how many seconds to wait before assuming the connected device is no longer available. If your server is very laggy, you may need to increase this, but be wary of the RTTs that the Supervisor and Coordinator show on their front panel screens.
After that, for a very basic level of security/utility there is the connection range, which prevents the Coordinator from receiving any network packets that are beyond this distance away. A value of 0 disables this feature, allowing packets from any distance. Note, cross-dimensional packets (such as nether to overworld) have a nil distance, so with this feature enabled they will always be ignored.
Finally for network configuration is a more solid security feature (solid enough for a block game). You can provide a passkey as a facility key (same for every device on your network) that will be used to perform an HMAC-MD5 message authentication hash on each packet transmitted and received over a wireless network. This verifies packets received are authentic and from one of your devices. It does NOT encrypt your data (that takes far too long), but there should be no need for it to do so. This feature prevents others from connecting to or even controlling your system.
Please DO NOT USE ONE OF YOUR REAL PASSWORDS. This key is stored in plaintext (human readable), so anyone who has access to that computer or the server's filesystem (like admins) can see it.
Before reaching the summary page, you will configure logging. This is likely to be unmodified, unless you want to store log files on a separate disk in-game for storage size reasons. That would allow for larger log files.
- Log file modes are either "replace the log file each time the main Pocket program starts" (not recommended) or "append to the log file each time the main Coordinator program starts" (recommended)
- Log path should be a valid path to somewhere that a file can be created, otherwise the system will error on start
- Debug messages are only really valuable for finding bugs of course, so if you have a problem and can send more detailed logs by reproducing the problem with debug messages enabled, that's ideal. If you are out to break the program, you might as well enable debug messages before you attempt to do so so the logs are already there. Do be aware this results in significantly larger log files, which may cause them to be recycled (cleared and restarted) more often if there are space problems.
Lastly, you will see an overview of all the configurations that are going to be applied. Auth keys are hidden in this view until you use the unhide button (this does not affect how they are stored).
Once you apply, you will see this screen.
Or this one if there was somehow a problem saving the settings.
