Expose forwarding related configuration data in ProxyConfig.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Currently, the ProxyConfig interface does not expose anything related to player info forwarding. This is quite unfortunate if you need to access the forwarding mode (and secret) from your plugin. (For example, to send the secret to a built-in limbo).
The workaround to this issue is quite simple, import the velocity API implementation, cast the configuration to VelocityConfiguration, and then you can get the forwarding config. But, I believe that it is quite unfortunate to need to use the velocity API implementation directly.
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 locating the ProxyConfig interface and the existing forwarding configuration implementation. Expose the forwarding mode and secret through the public interface so plugins can access them without casting to the Velocity API implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100