If you appreciate the work done within the wiki, please consider supporting The Cutting Room Floor on Patreon. Thanks for all your support!

Proto talk:Pokémon Diamond and Pearl/March-August 2006 Source Leak/Initial March 12 SDAT commit

From The Cutting Room Floor
Jump to navigation Jump to search
This is the talk page for Proto:Pokémon Diamond and Pearl/March-August 2006 Source Leak/Initial March 12 SDAT commit.
  • Sign and date your posts by typing four tildes (~~~~).
  • Put new text below old text.
  • Indent replies by prefixing with a colon :
  • Add new sections with the 'Add topic' button at the top right.
  • Be polite.
  • Assume good faith.
  • Don't delete discussions.
  • Be familiar with the talk help page.

Some Complications

As I've mentioned before the source code leaks are a bit tricky to document because we have something a lot more comprehensive than a few prototypes, we've got a huge number of commits and conceivably all of them may be buildable. So far, it looks like there's probably only a few key milestones which are buildable, but that may be subject to change.

Point is, individual file commits can be documented a lot easier than if all we had was builds, but then these assets are arguably not appropriate for a Proto: page. But would a Prerelease: page be any better? Maybe for assets that don't get compiled into the game, sure, but for files that do it's hard to tell.

I previously added a few todo notes to this page and due to the complications surrounding documenting fully version controlled source code these have (understandably) been removed from the page. That said, I think they're still something to think about rather than ignoring entirely. One additional complication, for instance, is that there aren't any commits between mid-April and late June, and so there certainly is some merit in grouping collections of files or builds from similar dates together.

As a record, here are the todo notes I suggested for the page:

  • Comparisons to final, e.g. by putting the final tracks here too (I think this is still valid)
  • Specify which builds use this SDAT (if any?)
  • Alternatively link to this page when a page is created for a build which uses this SDAT

These are mostly just some thoughts rather than a specific conclusion. I'd like to see what others have to say about whether we approach this from a Proto: or a Prerelease: perspective, but due to the quantity of dates that seemingly can't be built into files, I'm thinking some sort of middle ground (document which builds can be built, document revision histories of individual files, document how these files relate to the builds) might be optimal, but I fully see the perspective that as these builds do actually have to be built first it's arguably more comprehensive to focus on the individual file changes.

An alternative suggestion might be to group similar SDAT commits together and compare the small changes between them too, to cover more ground with a single page.--Hwd45 (talk)10:40, 29 July 2020 (UTC)