I was thinking that it could be done on the 68k if dlls were made for each card set and appvars for each card sets. That means the variety in your deck would be limited to what you can fit on your calc, or what you choose to fit on it.
I was thinking a similar thing could be done on the z80 calcs with appvars. I was thinking that executable could be stored into appvars and then copied to RAM by the MTG APP, hopefully acting similar to a dll. Then another appvar will contain the data for that card set. Obviously, this gives 84+SE users an advantage over 83+BE users because they can store many times more cardset dlls and data.
One problem is the linking though. The dlls have to be designed so that only one person needs the dlls in order to work. Most likely, some kind of switch master calc design.
I too have a lot of projects to work on first. You guys are still expecting my first project, and then after than N, and maybe my RPG, but if you guys really want, I'll defer the RPG and make MTG a major project goal after I've gotten more experience.
btw, can somebody explain the stack to me? not the z80's hardware stack, i mean order of resolution in Magic. I never played w/ that, but it turns it can be important.
edit:
QUOTE |
If it isn't possible due to the extreme complexity of the game, I think core set rules would suffice. There are enough core sets going round, and core set is easier (simpler and fewer abilities) to play. |
I think core rules (flying, first strike, haste, trample, *walks, protection from *, and anything I'm forgetting from Xth edition) shouldn't be a dll, and should be part of the main app/program. The dll compatibility is just an idea to possibly expand on the normal abilities. However, for people to continue updating w/ new cardsets, the way the main program interfaces with the dlls will have to be VERY VERY WELL documented.