Skip to content

Per server IP & profile forwarding configuration#291

Closed
mikroskeem wants to merge 12 commits intoPaperMC:dev/2.0.0from
mikroskeem:feature/per-server-forwarding-configuration
Closed

Per server IP & profile forwarding configuration#291
mikroskeem wants to merge 12 commits intoPaperMC:dev/2.0.0from
mikroskeem:feature/per-server-forwarding-configuration

Conversation

@mikroskeem
Copy link
Contributor

I heard that this feature is requested a lot, besides it's a feature that I need myself.

Use cases of this feature:

  1. You have servers with different versions in your network - some are as old as 1.7.10, some are 1.15.2. Sadly you'd have to use legacy forwarding then, instead of modern.
  2. You use different server software in your network - some servers run Paper, some run 1000$ shady MC-Market fork which doesn't support Velocity forwarding mode. Also forced to use legacy forwarding then.
  3. You don't like having huge Handshake packet.

This PR attempts to solve this issue by adding configuration option per server which allows you to configure what IP & profile forwarding should be used.

Will very likely involve changing configuration file structure sadly, but it's for the greater good.

PR is marked draft, code will be pushed as I'll work on implementing this into my network.

@astei astei added the type: feature New feature or request label Apr 12, 2020
@astei astei mentioned this pull request May 5, 2020
@mikroskeem mikroskeem force-pushed the feature/per-server-forwarding-configuration branch from f96a47e to 9ef9eb1 Compare May 8, 2020 00:07
@mikroskeem mikroskeem force-pushed the feature/per-server-forwarding-configuration branch from 7c3877c to 0a5d2f1 Compare June 16, 2020 13:56
@mikroskeem mikroskeem force-pushed the feature/per-server-forwarding-configuration branch from 0a5d2f1 to 5379dba Compare June 16, 2020 15:47
@mikroskeem
Copy link
Contributor Author

Will be rebased on top of Velocity 2.x.x because of needed API changes.

@astei astei added this to the Velocity 2.0.0 milestone Jul 16, 2020
@mikroskeem mikroskeem changed the base branch from dev/1.1.0 to dev/2.0.0 January 23, 2021 02:35
@mikroskeem
Copy link
Contributor Author

I'm not interested in continuing it this time. Someone else may pick this up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants