Expose player info forwarding in the API ( Fix #1063 )

[kyngs]

Fix #1063

[hugmanrique]

Thanks! 😀 (The CI fails due to an incorrect order of imports)

[kyngs]

Hang on, gotta make checkstyle happy with the import order

[Xernium]

This requires approval by @astei as he made a very deliberate effort in ensuring this does not get exposed to the API.

[kyngs]

This requires approval by @astei as he made a very deliberate effort in ensuring this does not get exposed to the API.

May I ask the reason?

[electronicboy]

The intention is to avoid exposing implementation details to plugins, especially given that things like Configuration are not API

I do wonder the use-case for this sorta thing, the forwarding mode should be effectively transparent to plugins, and have no real impacts elsewhere

[kyngs]

I do wonder the use-case for this sorta thing, the forwarding mode should be effectively transparent to plugins, and have no real impacts elsewhere

My practical use case is setting up nano limbo on-demand from the proxy. To do so, I need to forward the forwarding configuration to it.

[kyngs]

Any update?