It seems as though the workaround proposed in #12 for adding shared shockers by manually referencing them by ID in a group's configuration no longer works now that ShockOSC has moved to being an OpenShock module. Whenever I start the app, the list of shocker IDs in my group is typically overwritten with an empty array. And even if that doesn't happen for whatever reason, the shock message never actually seems to be delivered to OpenShock - I can see from the logs that the OSC message is being received and the group is being triggered, but the shock isn't actually delivered. I can sign into my partner's account on my machine to resolve this, but then the chat messages don't attribute who triggered the shock; also, while I'm okay with sharing logins with my partner, I understand it's not a solution for everyone.
I know the proposed workaround is an unsupported configuration, so for now, it seems like reverting to the pre-modularization version of ShockOSC is the path forward, and that's okay with me. I just wanted to see if there were any interest in potentially picking this back up. I'd even potentially be willing to take a stab at it, although I'm a little rusty with C#.
It seems as though the workaround proposed in #12 for adding shared shockers by manually referencing them by ID in a group's configuration no longer works now that ShockOSC has moved to being an OpenShock module. Whenever I start the app, the list of shocker IDs in my group is typically overwritten with an empty array. And even if that doesn't happen for whatever reason, the shock message never actually seems to be delivered to OpenShock - I can see from the logs that the OSC message is being received and the group is being triggered, but the shock isn't actually delivered. I can sign into my partner's account on my machine to resolve this, but then the chat messages don't attribute who triggered the shock; also, while I'm okay with sharing logins with my partner, I understand it's not a solution for everyone.
I know the proposed workaround is an unsupported configuration, so for now, it seems like reverting to the pre-modularization version of ShockOSC is the path forward, and that's okay with me. I just wanted to see if there were any interest in potentially picking this back up. I'd even potentially be willing to take a stab at it, although I'm a little rusty with C#.