- Joined
- Jan 26, 2009
- Messages
- 2,570
- Trophies
- 0
- Age
- 42
- Location
- Philippines
- Website
- nonwhatso.blogspot.com
- XP
- 687
- Country
Reading through some of your posts, i think we are all coming to terms with the underlying idea, it's just that some of the process is different according to each of you. a few like myself suggest a separate app, but one suggests that the firmware do it, but they all do the same thing. let me break it down like this:
instead of:
That's the underlying idea, and i think everyone seems to understand that doing it this way, it becomes possible for updates to already published games without resorting to republishing of updated cartridges.
basically, what the game launcher does is it has a list of data it can update, intercepts requests for that data and instead points it to updated data and assets from the DLC and feeds that data to the game engine requesting it.
example, for fighting games, when the game engine asks for assets for the character selection screen, the game launcher intercepts that, points it to the DLC where it finds an updated character selection screen with an additional row of new DLC characters and feeds it to the game engine. of course, the game launcher must satisfy a few conditions.
It must have the ability to override the game engine, because the data requested will be different from the one it receives, and this almost always ends up with an error. the game launcher must be able to "persuade" the game engine that the data it just received is okay and workable. i actually thought about everything possible to think about this idea, from the way it works with game data, to who must provide the information the application needs in order to "cheat" and "hack" the game (the game devs), to how multiplayer can work, to security issues, to download play, to profit from DLC microtransactions--everything.
I threw it all into one big ass letter, sent it to someone who blogs about videogames, and hopes he/she can pass it on to someone who will take these ideas seriously. because it's from the internet.
okay, that last part was half-kidding.
instead of:
QUOTE said:Boot Game Cart from Home Menu> Game assets loaded> playing the game
we do this instead:
QUOTEBoot Game Launcher> Game Launcher boots Game Cart > Plays the game with DLC
That's the underlying idea, and i think everyone seems to understand that doing it this way, it becomes possible for updates to already published games without resorting to republishing of updated cartridges.
basically, what the game launcher does is it has a list of data it can update, intercepts requests for that data and instead points it to updated data and assets from the DLC and feeds that data to the game engine requesting it.
example, for fighting games, when the game engine asks for assets for the character selection screen, the game launcher intercepts that, points it to the DLC where it finds an updated character selection screen with an additional row of new DLC characters and feeds it to the game engine. of course, the game launcher must satisfy a few conditions.
It must have the ability to override the game engine, because the data requested will be different from the one it receives, and this almost always ends up with an error. the game launcher must be able to "persuade" the game engine that the data it just received is okay and workable. i actually thought about everything possible to think about this idea, from the way it works with game data, to who must provide the information the application needs in order to "cheat" and "hack" the game (the game devs), to how multiplayer can work, to security issues, to download play, to profit from DLC microtransactions--everything.
I threw it all into one big ass letter, sent it to someone who blogs about videogames, and hopes he/she can pass it on to someone who will take these ideas seriously. because it's from the internet.
okay, that last part was half-kidding.