Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature]: Implement the NATTraversalReportInternal protocol #75

Open
1 task done
jonbarrow opened this issue Jun 1, 2024 · 2 comments
Open
1 task done

[Feature]: Implement the NATTraversalReportInternal protocol #75

jonbarrow opened this issue Jun 1, 2024 · 2 comments
Labels
awaiting-approval Topic has not been approved or denied feature A feature request

Comments

@jonbarrow
Copy link
Member

Checked Existing

  • I have checked the repository for duplicate issues.

What feature do you want to see added?

An implementation of the NATTraversalReportInternal protocol.

Why do you want to have this feature?

Not used by NEX, but is provided by Rendez-Vous. Will be useful to people making non-NEX game servers. Also makes the library more feature complete.

Any other details to share? (OPTIONAL)

This is an internal protocol.

Documentation link: https://nintendo-wiki.pretendo.network/docs/nex/protocols/nat-traversal-report-internal
@jonbarrow jonbarrow added awaiting-approval Topic has not been approved or denied feature A feature request labels Jun 1, 2024
@DaniElectra
Copy link
Member

Do we really need to implement internal protocols?

@jonbarrow
Copy link
Member Author

jonbarrow commented Jun 2, 2024 •
edited
Loading

We don't need any of the 31 protocols in the current set of issues. They're there just for the sake of completion. Do we have reason not to?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
awaiting-approval Topic has not been approved or denied feature A feature request
Projects
Pretendo Tasks and Goals
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonbarrow @DaniElectra