Dev team calls

Since December of 2024, the dev team has been holding a Discord call every 2 weeks to make decisions on whether to approve new features and to talk about a variety of other topics related to OoTR development. This article is an archive of summaries of each call, ordered reverse-chronologically.

The next call will be held on April 7, 2025 at 22:00 UTC.

March 23, 2025

Participants: Fenhl, Kirox, RealRob, TreZ

1. changelog PR: rebase and incorporate flagrama's suggestion, then merge
2. new magic model: test scroll with smoke, otherwise go with jar with rainbow smoke, merge stick/nut upgrades with smoke as well before release
3. merge Dev-R changes into main Dev:
   • mixed pools changes blocked on #2332
   • investigate what this fishing change does and whether it's still wanted
   • extra cosmetics can probably just be PR'd
   • fast skulltula text should probably be a setting (included in glitched logic 3.0 PR, needs to be separated out)
   • GUI tweaks → some of it seems like a good idea, compromise on Fenhl's branch to be PR'd and discussed
4. allow unequipping swords/shields? Ask for feedback

February 24, 2025

Participants: Fenhl, Kirox

1. went through some open issues and PRs for review/testing
2. do we want to advertise the list of good first issues more? (e.g. a pin in #dev-public-talk or a post in #dev-resources)
3. new schedule for these calls → rotating schedule?

February 10, 2025

Participants: Fenhl, Kirox, RealRob, ShadowShine57, TestRunner

1. mentoring program: ASM/C hacking guide will be published as a written document, Rust crash course as a call if TreZ is still interested
2. added #2369 to the blocking issues for the next release
3. went through most of the open issues under consideration, continue next time
4. regarding #851: reconsider integrating RSL script into randomizer in some form, talk to RSL organizers
5. regarding #1647: RealRob will ask owl is not a cat whether this makes sense to attempt

January 27, 2025

Participants: Fenhl, TestRunner, TreZ

1. followed up on release blocking issues: re-requested review on #2345 from RealRob, options for making the magic meter model more distinct from prescription on VC (increasing opacity of the bottle, changing paper color to be more distinct) → asked Kirox to try implementing distance-based opacity, if not easily doable, make a fallback PR that just increases the opacity
2. ice trap model (#dev-public-talk post): looks good, how would it interact with possible future trap types? → new trap types don't have to come with a model since it's only displayed when picked up
3. set up automation for releases, see #dev-public-talk post
4. new macOS icon made, TreZ will PR along with new Windows icon
5. new dev team member RealRob
6. integrate oot.flagrama.com downpatcher into the randomizer? → TreZ will look into it regarding the web patcher, flagrama doesn't think it's a good idea
7. new contributing guidelines document that will go in the repo (CONTRIBUTING.md) and replace an outdated #dev-public-talk pin that still mentioned Trello → Fenhl will write a draft and post in #dev-private-talk for review before PRing

January 13, 2025

Participants: Fenhl, Kirox, ShadowShine57

1. setting to add specific dungeon reward requirements for the rainbow bridge (e.g. Light medallion + Forest medallion + Goron ruby)
2. move relevant Trello tasks to GitHub issues
3. went through all PRs under consideration
4. use the settings migration feature also to avoid breakage when settings types change?
5. ask Roman about the status of the extra cosmetics on Dev-R

December 16, 2024

Participants: Fenhl, Kirox, TestRunner, TreZ, Zannick

1. legal implications of using decomp code → TreZ thinks it's fine
2. update compressor/decompressor to MIT-licensed versions?
3. remove binaries from git repo and generate Dev versions in CI?
4. optimization — mypyc, rewriting performance-critical parts in C/Rust? (see PyO3)
5. check why the fuzzer is disabled, potentially reenable
6. mentoring issues e.g. #2106 for decomp-based fixes
7. publish these notes on the OoTR wiki
8. offline releases: new icon (new macOS icon shape), automation, Universal binary for macOS
9. release numbering: previously based on whether there were big features added — now that we have a release schedule, use major version bumps for scheduled releases and minor version bumps for hotfixes and preset backports?
10. postpone the feature freeze by a week to allow people to work on features for this release during holidays? → ask in #dev-public-talk
11. next call on January 6 due to holidays postponed to January 13

December 5, 2024

Sketch of the proposed magic meter model

Participants: Fenhl, ShadowShine57, TestRunner, TreZ

1. considering moving the Python files from the root of the repo to a subfolder to clean things up a bit, not sure if it's worth the extra work for PR authors
2. idea to allow individual options of dropdown/multiselect settings to have separate tooltips → does the UI framework support this?
3. new magic meter model: making it a cosmetic setting would be bad for watching other runners, new idea see image, Maple will look into it
4. approved some nominated PRs, left comments on others, asked race mods^{[private link]} about #2302
5. to encourage work on features we want to see (e.g. stats screen), we could put up bounties, open tracking issues, and/or create feature branches directly on the OoTRandomizer fork
6. triforce-pog-rework branch can probably be deleted, it only exists because the repo was still TestRunner's personal fork when it was created
7. we can assign PRs to ShadowShine57 for review
8. separate Discord channel for nominations? → not necessary
9. next call on the 16th (Mondays work better for TestRunner), maybe start an hour earlier if that makes it possible for Kirox to join? (though ShadowShine57 would most likely have to join late then)