<11muxxer.exe> Made some more progress, still missing a lot, of course
2024-08-19 23208, 2024
logistic-bot joined the channel
2024-08-19 23235, 2024
discordbrainz
<11muxxer.exe> Decided that there should be a Game (equivalent to both an Artist and a Release Group) and a Release. Games will have, apart from basic metadata: * Type (Game, Compilation, Remaster, Remake, Demake, possibly something else) * Additional content (middle table associated with DLC, expansions, etc.) Releases, on the other hand, will contain very detailed metadata, including so far: * Release date. * Booleans for
2024-08-19 23235, 2024
discordbrainz
singleplayer, multiplayer, coop, LAN and MMO. * Max players supported in a single game session (if applicable) * ESRB rating ('RP', 'EC', 'E', 'E10+', 'T', 'M', 'AO'), if applicable. * PEGI rating ('3', '4', '6', '7', '11', '12', '15', '16', '18'), if applicable. * CERO rating ('A', 'B', 'C', 'D', 'Z'), if applicable. * Possibly some other rating systems, later. * Max width and height for the resolution. * Standard framerate (if
2024-08-19 23235, 2024
discordbrainz
applicable) * Booleans for NTSC, PAL and SECAM (if applicable) * Booleans for Mono, Stereo, 5.1 and 7.1 Audio * Medium * Packaging * Serial/catalog number * Barcode/UPC * Middle table for platforms * Middle table for DLC * Secondary table for peripherals officially supported by the game * Secondary tables for ESRB, PEGI and CERO descriptors/markers * Secondary table for languages (UI, Audio, Subtitles) * Secondary table for system
2024-08-19 23235, 2024
discordbrainz
requirements for PC releases
2024-08-19 23245, 2024
discordbrainz
<11muxxer.exe> Any objections or missing stuff?
2024-08-19 23253, 2024
scrumplex_ joined the channel
2024-08-19 23240, 2024
scrumplex has quit
2024-08-19 23218, 2024
Lotheric
muxxer.exe, CAnada uses ESRB but the province of Quebec uses PEGI
2024-08-19 23245, 2024
Lotheric
not sure if it's of any uses to you
2024-08-19 23246, 2024
Lotheric
:)
2024-08-19 23257, 2024
yano has quit
2024-08-19 23224, 2024
yano joined the channel
2024-08-19 23202, 2024
mven97 has quit
2024-08-19 23210, 2024
MeatPupp3t has quit
2024-08-19 23222, 2024
MeatPupp3t joined the channel
2024-08-19 23229, 2024
ArchieButtle[m] joined the channel
2024-08-19 23229, 2024
ArchieButtle[m]
Are you attempting to snapshot a game in time (i.e. a conventional disc release), or does a release also sometimes represent a "live" game? How do you handle live update version increments, or conversely offline patch exes, etc -- sub-release indexing?
2024-08-19 23215, 2024
ArchieButtle[m]
Though then there's also the consideration that a single patch file may target multiple releases, and so on...
[13:12] discordbrainz <muxxer.exe> I'm thinking that if we are to add every single major rating system for each country, it would be hard to manage, too many tables.
2024-08-19 23251, 2024
MonkeyPython
sortof thing sounds liek dynamic attributes
2024-08-19 23209, 2024
MonkeyPython
[14:23] discordbrainz <elomatreb> expanding a schema later is perfectly possible <--very agrree with tis
2024-08-19 23222, 2024
MonkeyPython
mb itself didn't start with advanced relationships even so
2024-08-19 23242, 2024
MonkeyPython
[14:24] discordbrainz <elomatreb> MB didn't start with Works, relationships, Events, Series, etc. either
2024-08-19 23242, 2024
MonkeyPython highfive elomatreb
2024-08-19 23245, 2024
Island joined the channel
2024-08-19 23259, 2024
xoip has quit
2024-08-19 23204, 2024
xoip joined the channel
2024-08-19 23255, 2024
reosarevok[m] joined the channel
2024-08-19 23255, 2024
reosarevok[m]
<MonkeyPython> "sortof thing sounds liek dynamic..." <- Dynamic attributes seems about right
2024-08-19 23219, 2024
beanbrain joined the channel
2024-08-19 23227, 2024
discordbrainz
<11muxxer.exe> French being french
2024-08-19 23255, 2024
discordbrainz
<11muxxer.exe> ArchieButtle: I haven't really thought of it yet, the database might just use the latest or final version of a game. These days it's rather unrealistic to expect games to be final because even 2-decade old games get updates, such as Half-Life or Counter-Strike 1.6. Alternatively, given we'd want to include as much useful metadata as possible, each release could have a version history which could also mention previous
2024-08-19 23255, 2024
discordbrainz
metadata
2024-08-19 23203, 2024
discordbrainz
<11muxxer.exe> In which case it'd be more sensible, perhaps, to use "Release" as more of a release group which contains the metadata for different versions within
2024-08-19 23251, 2024
discordbrainz
<11muxxer.exe> So, at the end, you'd have a hierarchy that would work like: [Game] has [Release] has [Version] Minecraft has Minecraft: Java Edition ( PC release ) has [Beta 0.7, 1.1, 1.2, etc]
2024-08-19 23240, 2024
discordbrainz
<11muxxer.exe> Perhaps the versions could work as recordings so that multiple releases might share them
2024-08-19 23221, 2024
discordbrainz
<11muxxer.exe> But depends on the metadata, otherwise these versions could not necessarily be standalone entities
2024-08-19 23235, 2024
discordbrainz
<11muxxer.exe> Because it's also important to note that, at the end of the day, there still will be some differences between versions for games. Release A for a Game might support up to 1080p, and so does Release B. Both releases are updated to version 1.1 and now release A supports 4K, while Release B still is limited to 1080p.
2024-08-19 23256, 2024
discordbrainz
<11muxxer.exe> Because of this, it'd make sense to keep release versions as exclusive to each release instead of being shared entities, unless we were to structure the data differently, but I can't currently think of any proper way to do so that wouldn't require overcomplicating the database model.
2024-08-19 23223, 2024
beanbrain has quit
2024-08-19 23218, 2024
logistic-bot joined the channel
2024-08-19 23208, 2024
Zhele_ has quit
2024-08-19 23233, 2024
Zhele_ joined the channel
2024-08-19 23239, 2024
logistic-bot has quit
2024-08-19 23211, 2024
iconoclasthero has quit
2024-08-19 23235, 2024
iconoclasthero joined the channel
2024-08-19 23224, 2024
discordbrainz
<05RandomMushroom128> >any missing stuff? how far do you want to go with this 😭 for tracking how far you are in every game: individual worlds / levels (can be linked with videobrainz: walkthrough for level?) quests, objectives, dungeons collectibles, achievements i'd love to have these too: game mods, texture packs, rom hacks another thing to add: what about games or services that players can publish content on? like super mario
2024-08-19 23224, 2024
discordbrainz
maker levels, roblox games or minecraft server minigames
<aerozol[m]> "bitmap: So cool! When adding a..." <- ooh nice one!
2024-08-19 23231, 2024
aerozol[m]
“what are the chances”
2024-08-19 23215, 2024
d4rkie has quit
2024-08-19 23241, 2024
d4rkie joined the channel
2024-08-19 23201, 2024
anonn has quit
2024-08-19 23237, 2024
sentriz has quit
2024-08-19 23218, 2024
sentriz joined the channel
2024-08-19 23240, 2024
everypizza[m] has quit
2024-08-19 23204, 2024
discordbrainz
<11muxxer.exe> Not that far. I don't think metadata for levels, worlds or such would be a good idea, specially if you consider games with procedural generation or with a massive amount of levels/worlds (such as Spore). Cover arts and official trailers are in my mind, but walkthroughs probably not, might just link an IGN guide instead.
2024-08-19 23230, 2024
discordbrainz
<11muxxer.exe> As for community-made content, I'll tackle that down later, for now I'm only thinking of including standalone games and official additionla content.
2024-08-19 23254, 2024
discordbrainz
<11muxxer.exe> The idea is to not include the content of the game itself for the metadata, but, I mean, well, the metadata.
