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

Best of three (in progress) #4076

Closed
wants to merge 2 commits into from
Closed

Best of three (in progress) #4076

wants to merge 2 commits into from

Conversation

Zarel
Copy link
Member

@Zarel Zarel commented Oct 22, 2017

This is a WIP of a PS best-of-three implementation. It's actually nearly completely finished, it just looks kind of ugly, mostly because client support for non-battle gamerooms needs to be improved.

@scheibo
Copy link
Contributor

scheibo commented May 26, 2019

Obviously this is going to need to be updated to handle the recent RoomGame refactor, but could you elaborate on how "client support for non-battle gamerooms needs to be improved"? It sounds like something which may be blocked on the Preact rewrite?

@Zarel
Copy link
Member Author

Zarel commented May 27, 2019

Obviously this is going to need to be updated to handle the recent RoomGame refactor, but could you elaborate on how "client support for non-battle gamerooms needs to be improved"? It sounds like something which may be blocked on the Preact rewrite?

Yes, that's correct. The main issue I was dealing with was that music was playing and I wasn't very good at turning it off.

@scheibo
Copy link
Contributor

scheibo commented May 28, 2019

The main issue I was dealing with was that music was playing and I wasn't very good at turning it off.

If this is all that is required, does this really need to be blocked on Preact? The BO3 feature seems to have enough popularity that it seems potentially worth duplicating work if someone wanted to pick it up and deliver it sooner provided the required effort is relatively small (compared to say, the Friend's List)?

@Zarel
Copy link
Member Author

Zarel commented May 29, 2019

I should probably refactor BattleSound, yes. That's certainly a refactor that can land before a full Preact rewrite because it's in the .ts files already used by the old client.

@scheibo
Copy link
Contributor

scheibo commented Jul 24, 2020

I should probably refactor BattleSound, yes. That's certainly a refactor that can land before a full Preact rewrite because it's in the .ts files already used by the old client.

Given a refactor of BattleSound recently occured, is BO3 actually still blocked on Preact?

@Zarel
Copy link
Member Author

Zarel commented Jul 24, 2020

Oh, no, this hasn't been blocked on Preact since forever. I did the relevant BattleSound refactor in Aug 2019:

smogon/pokemon-showdown-client@f1a560f

At this point, this mostly just needs to be rebased.

@DaWoblefet
Copy link
Member

Superseded by #9793

@DaWoblefet DaWoblefet closed this Oct 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants