Okay so I thought I'd post this message in this forum instead of the "Homebrew" forum because it is more about *legal/official* Nintendo Slot-1 Cartridges. I have purchased several (a dozen of so) Nintendo DS/DSi games... And I have never seen Nintendo requiring to *update* or *patch* the game with a newer version. Okay you can update the DS/DSi System version while connecting to the Internet... But I'm interested in Nintendo GAMES. Why the curiosity? Well what I am trying to know is how *Officially* Nintendo would handle a game that REQUIRES updates... Suppose my *super new game ZYX* is released using official Nintendo means as a *cheap* Slot-1 Cartridge (maybe like $15.00 for a new one). The game will contain all of the game logic required to play ... AT THAT MOMENT. But suppose my game *expands* and includes NEW game assets... How would Nintendo handle *patching* or *updating* the game such that the logic for new game assets is present... Firstly let me say, I'm not a WOW developer... So I don't think I want my game to include a Scripting Engine like "Mono". That would just complicate the already challenging effort of developing a DSi game. A scripting engine could probably allow for dynamic code to be downloaded along with new game assets... I think this concept is COOL - but too complicated. So my alternative would be to have updates for the game. So version 1.0 could support X and version 2.0 could support X and Y... Incremental updates to the *core* of the game such that newer game assets can be handled by the DSi client. I have seen DSiWare, and it just looks like games you can download for *credits* (Points). I don't see anything about *versions*. Secondly I think people would really get p!ssed off if the updates were not FREE to download... How can any of this be handled by the conventional (or Official) Nintendo policies (Slot-1 Catridges). Many thanks for your help and input! Note: I would love it if somebody could tell me if something like LUA (http://www.lua.org) could be embedded into a DSi client. So far I have not seen anything about Shared Libraries (like DLLs), everything seems to need to be Static Libraries.