[VELOCITY] swapping servers does not auto-start server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 391
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I have vane-admin configured to autostop some of the servers in my velocity network and I have vane-velocity configured to auto-start servers. This is working for the initial join, whatever server the client goes to first will properly autostart. The problem is once a client is connected and in the network, if they use the velocity /server command to swap servers, if their target server is offline, the autostart logic in vane-velocity never fires. The user just gets an error message saying that they were unable to connect and to please try again.
Is it possible to have vane-velocity start a server when a client connects to it via the /server or /send commands?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing vane-velocity's handling of the Velocity /server and /send commands, then compare it with the existing autostart path used when a client initially joins. Reproduce the failure with an offline target server; done means either command starts the target and connects the client, with the existing error behavior preserved for failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100