Add a new DefaultPort row in the Services table that determines the default controller port for that service. This would allow IRC and Twitch to have different ports by default, for instance.
Decide if the user's port setting should override the service's default port.
Add a new **DefaultPort** row in the **Services** table that determines the default controller port for that service. This would allow IRC and Twitch to have different ports by default, for instance.
Decide if the user's port setting should override the service's default port.
Perhaps the service's default port should override the user's. Right now all existing installs would have user ports at 0 or greater. To use the service's port, a user would have to set their port to -1 or some other value, which isn't as practical.
On the other hand, the host can set the service's port to -1 to use user ports and 0 or greater to enforce a specific default port. This is much easier to manage and takes the burden off the users. ControllerPortCommand messages can be adjusted to notify users that their port is overridden.
Specifying ports in the input syntax would work as usual - "&2a" would still press "a" on port 2.
Perhaps the service's default port should override the user's. Right now all existing installs would have user ports at 0 or greater. To use the service's port, a user would have to set their port to -1 or some other value, which isn't as practical.
On the other hand, the host can set the service's port to -1 to use user ports and 0 or greater to enforce a specific default port. This is much easier to manage and takes the burden off the users. `ControllerPortCommand` messages can be adjusted to notify users that their port is overridden.
Specifying ports in the input syntax would work as usual - "&2a" would still press "a" on port 2.
Add a new DefaultPort row in the Services table that determines the default controller port for that service. This would allow IRC and Twitch to have different ports by default, for instance.
Decide if the user's port setting should override the service's default port.
Perhaps the service's default port should override the user's. Right now all existing installs would have user ports at 0 or greater. To use the service's port, a user would have to set their port to -1 or some other value, which isn't as practical.
On the other hand, the host can set the service's port to -1 to use user ports and 0 or greater to enforce a specific default port. This is much easier to manage and takes the burden off the users.
ControllerPortCommandmessages can be adjusted to notify users that their port is overridden.Specifying ports in the input syntax would work as usual - "&2a" would still press "a" on port 2.
Put on hold for another release.