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.

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

ygopro compatibility #144

Open
Timtam opened this issue Dec 18, 2017 · 3 comments
Open

ygopro compatibility #144

Timtam opened this issue Dec 18, 2017 · 3 comments

Comments

@Timtam
Copy link
Collaborator

Timtam commented Dec 18, 2017

It would be amazing to have a ygopro server as well. Now that we have rooms, sighted players would be able to join a room with their ygopro client of choice and duel against mud players directly.

@JessicaTegner
Copy link
Contributor

Hi.
What would be the steps we would need to take in order to do this @Timtam

@Timtam
Copy link
Collaborator Author

Timtam commented Dec 30, 2019

Quite a few, the entire server would need to be re-structured and partly rewritten. We'd need to reverse engineer the server messages required to configure and initiate a duel from within a sighted client (YgoPro2 for example). There is a mercurial server out there somewhere that we should re-implement partly here. Then we'd need to write a duel backend that can receive, understand and respond to YgoPro client duel commands and communicate with our own current duel system to exchange messages and translate whatever action the other player does to the corresponding message set. That would over all take quite a long time and would require alot of reviewing, testing and probably at least a few unit tests to be sure that the critical parts work well. Proper error handling/debugging would be necessary too. We'd first need to find out how the duel negotiation works in YgoPro2, so that we can rewrite our system to work the same way. i'm pretty sure that I already worked alot into the right direction though.

@Timtam
Copy link
Collaborator Author

Timtam commented Nov 5, 2020

Thats more of an evaluation ticket to extrapolate the required steps to take, as Nicklas already suggested. The implementation needs to be defined in much more granular steps later on.

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

No branches or pull requests

2 participants