add Support for 1.12.2 modern forwarding
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
Requested Feature
add support for 1.7.2 to 1.12.2 modern forwarding with PCF
Why is this needed?
to allow the server to use a more secure modern forwarding from 1.7.2 to 1.12.2
Alternative Solutions
Ive had to compile custom code to allow the client from 1.7.2 to 1.12.2 to be able to use modern forwarding by setting locks of 1.13 to 1.7.2
https://github.com/p0t4t0sandwich/Velocity/tree/feat/modern-forwarding-legacy
edited this with more things changed
Additional Information
No response
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 reviewing the linked feat/modern-forwarding-legacy branch and the Proxy-Compatible-Forge project to understand the proposed compatibility approach. Trace how Velocity handles modern forwarding for the affected protocol versions, then verify the result with 1.7.2–1.12.2 clients and servers. Done means those versions can use secure modern forwarding without custom patches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100