I don’t think we need to do this just yet, but Licho’s introduction of an error message on all springie autohosts instructing people to use ZKL does suggest that maybe we should have another plan ready in case springie keeps growing more specific to ZKL
So! Potential solutions
- I’ve already had a few nice chats with Zydox, who offered us space on his server using his python-based autohost swarm.
- Ask our great and benevolent Owner Of the Server (ie koshi) about the feasibility of a SPADS instance or Zydox host-swarm on his box.
- Worst case: try to patch together as much coverage as we can using [S44]Autohost and Yuribot
To my mind, the best approach is the first; even if koshi is ok with it, it’s a big ask in terms of system resources/yet another process running, and Zydox already has infrastructure running/hosting games regularly. The only tricky bit is figuring out how to update the hosted game version without asking Zydox directly - springie has a fairly nice tie-in with rapid where I can just submit the link to the version I uploaded to our webspace, and a few minutes later that’s the version that’s on the S44 springies.
Anyways this is all still hypothetical: best case scenario is that licho is cool with making exceptions for non-ZK autohosts in terms of juggler compatibility/doesn’t tie springie more tightly to ZKL.