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

Feature Request: More Flexible and Versatile Track Selection Options in the Custom Duel Menu #344

Open
Merik2013 opened this issue Mar 6, 2024 · 0 comments

Comments

@Merik2013
Copy link
Contributor

I've actually been workshopping this in ChatGPT the past week.
https://chat.openai.com/share/d88f7e50-d79d-4a0f-88b7-eedc49dc3261
It gets a bit long because I had to paste the entire DuelSettings.cs into it at one point. ChatGPT basically just reads headlines in Bing and can't actually read github pages, but that won't stop it from pretending it can.

Anyway, the idea is that currently the custom duel setting for BGM only allows you to pick a number between 1 and 16 (or however high the current standard duel BGM tracks go) and uses that to tell the game to pair DUEL_NORMAL, DUEL_KEYCARD, and DUEL_CLIMAX tracks with that number. With the addition of our ability to create custom sound tracks I'm now finding this very insufficient as it would prove difficult to pair 3 perfectly matching sound tracks for every occasion. This current method also can't grab BGM_SOLO or the special BGM_DUEL_EX tracks used for the WCS events.

Ideally, we should be able to manually select the first, second, and third tracks individually from their own drop down menus and be able to freely mix and match, just as we can in duel files. These windows should include virtually every file that starts with BGM_, and not limit what track can be assigned to what slot. I'm not entirely convinced of ChatGPT's final proposed solution to this. The above log is best perused by someone more familiar with the project's code.

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

No branches or pull requests

1 participant