Thats of course also an option.

But in the end it all is up to the people arranging the competition though.

dvik:

But uhm, who's talking about MSX2? The Dev rules state: should work on "MSX1 + x RAM + PSG". Who cares whichever extras are supported? That there may be an MSX2 palette as bonus doesn't mean it's suddenly a pure-msx2 game, it's still an MSX1 contest, and whatever extra is a bonus. In fact, a bonus *does* deserve a bonus point, as it's commendable that a team has managed to cram in extra features in the same ROM while it still runs without these extras. As far as I'm concerned, an MSX1 game may have features for Moonsound, Graphics9000, R800 .. all great, especially as it still runs on an MSX1 with x RAM and PSG. I'd say, it's a sign of 1337'ness if you actually know how to make a game which uniformly runs on MSX1 and a boosted 1337 system, and 1337'ness should be rewarded.. . As there's also stated in the rules, the bare MSX1 version will be judged. So, if you put all your attention to the G9k/Moonsound/R800 bits, chances are big that the MSX1 'version' is actually lacking behind. So, if you're to support all these extras you usually run the risk of ending lower in the ranks because the bare MSX1 version sucks.

As for 64k on PC: the comparison isn't much relevant here. I dunno if you've seen modern 64k intros, but they're all about media generation. I've done (and won ) my share with that stuff as well, years ago. 64kb is a lot of space for scripts and generators. On MSX 64kb will have to be compressed media if you want more than raw 64kb.

You may say that 64kb on msx could simply be 'a goal', in a way it could in fact be interesting for a different contest. But as far as I know the Dev contest is 'to generate new games for MSX1". Esp. in these recent years where Dev games are released on physical cartridges, I think any MSX1-user would be happy with *any* MSX1 game, small or large, so why exclude largeness? Some game types require quite some ROM space, think RPGs and really large shooters. Nemesis1 was size-comparable with Universe Unknown, so a game of that caliber could fit 48k ROM, but you'll see that Nemesis 2 actually uses quite the full ROM (try to RAR nem2 and nem1, and observe the difference). So, when Dev would limit its specs to 64k ROM, 16k RAM, then you can cancel out all Nem2 games and up. Question is of course "what's more important?"
- Having all kinda of games, small, large, epic, casual?
- Having a number of medium-size games which are specs-wise more close to eachother so that no-one feels like a mile behind?

I'd personally always choose the first option, even if we don't win. I rather spend my time on something I like (and sorry, but I like big stuff ), than on unusually smaller games just to fit the rules. (Don't look at RNFF, it was made from scratch in 3 days )

Actually, the specs from Dev7 were perfect, if you ask me.

can you stop writing 1337 tho, because it looks stupid

Quote:

dvik: I'd say, it's a sign of 1337'ness if you actually know how to make a game which uniformly runs on MSX1 and a boosted 1337 system, and 1337'ness should be rewarded..

Pardon my french but ... What the f*ck is a 1337 system and the 1337'ness

wolf_:

Although your formulation on the second option was intentionally written to sound bad I say definitely the second option.

I like msxdev to represent the early to mid 80's and not have that fluffy Moonsound or V9938 etc. It can be nice occasionally but I'm simply not interested in that. I'm a big MSX1 fan and don't care much about MSX2 probably because MSX1 is what I grew up with. MSX2 or fluffy MSX1 games could compete in for example the MRC competition instead. Leave msxdev to the core nice MSX1 specs of the mid 80's.

At Metalion... 1337 means "leet", and "leet" means "elite". 1337 means eliteness.

Quote:

At Metalion... 1337 means "leet", and "leet" means "elite". 1337 means eliteness.

I trough that someone wrote this as "Courier Elite" ...

1337.

Does anyone know how this is linked with US Robotics MODEM?
By the way, how to connect those things on MSX !?

Good news!!!

I "mean" how to program this protocol ... Since, obviously the RS-232C interface could be easily "plugged" into the MSX1 system.

Probably, there is something like 'this':
TCP PORT 1337

Yukio, what has this to do with MSXdev'08? Please get back on topic.

Let's try to explain how I see the issue:

Msxdev should try to keep the feeling of the original MSX1 games.

I'm for keeping the HW requirement as close as possible to the
bare bone MSX1 computer I had when I was child (Sony Hit Bit HP-75)

My reasons are personal and sentimental, but I think that
everyone here is on this forum for personal and sentimental reasons,
(otherwise why wasting time on a 20y old washing machine ? )

I had some konami megaroms in that period, and they were part of the same MSX1
experience I was mentioning when I say "feeling of the original MSX1 games".

So, IMHO, msxdev should allow scc megarom support.

As I told, there are no rational reasons behind my position above.

Actually, our current WIP is quite large and
it would be almost impossible to shrink it in 32K or 48K.
But this second fact does not affect my view on
msxdev rules (or not ) .

I'd still say: keep the dev7 rules. No-one is forced to fully use all specs, so if you want to do an uber-retro game, then go ahead. If a smaller game is better than a larger game (see dev7) it wins. It would be a pity when larger games like Monster Hunter etc. wouldn't be possible anymore. I think all these should remain at the Dev contest, not any of the MRC contests (as we may not always organize a challenge!). In addition, ARTRAG/Huey have their C point, which sounds rather valid to me. Hence: Dev7 specs ftw!

Well thats your opinion and I have another. In the end its really up to the msxdev team to decide anyways so I'm not sure how useful this discussion is.