DZ-Jay

Mr. Basic Meets Bits 'N' Bytes

ABPA® Backgammon

U.S. Ski Team® Skiing Or Mountain Madness: Super Pro Skiing

ADVANCED DUNGEONS & DRAGONS® Treasure Of Tarmin ® Cartridge

ADVANCED DUNGEONS & DRAGONS® Cartridge.

Las Vegas Poker & Blackjack.

Ah, come on! It wasn't sarcasm, just playful banter. :saint:

Is one of those things a poker and blackjack cartridge? Because I think I have a few of those. Let me know, I wouldn't mind trading those at all.

Nice try. I don't think you can reduce all human interactions and motivations to mere formulae. I suppose that if a person already knows that a re-release is imminent, whether in a day, a week, or a year; taking advantage of the collector and speculator market by exploiting insight knowledge is still distasteful, no matter how well it is planned to make it look coincidental. Again, it was only speculation on my part. I do not know if a re-release is forthcoming. It just occurred to me that it could be something that someone could do. dZ.

Ah, so if a new Blix comes out next week, it's purely coincidental, and not an attempt to maximize their take and profiting from an information imbalance. I guess that could be the case. Sure.

Sure, sure, but if a new release of Blix pops up in the next few months, what should we take away from this? I'm open to being wrong ...

Cool! I'm still waiting for someone to make this one -- not bad ... for an ugly Christmas sweater.

I guess I could be wrong. Did you have a license from Sega for Zaxxon? Or from Atari for Asteroids? Or from Stern for Aardvark? Or from the owner of Oh Mummy!? If so, then I stand corrected. In any case, my point was to applaud your effort of promoting the respect of copyrights in video game development. That seems to be a sensitive topic in retro-gaming communities, but it seems we should all be able to agree that the product of people's work and effort has value. -dZ.

Now, that is weirdly disturbing and creepy.

Do not open till ... Ah, shucks! Too late!!!

I guess it makes sense to those who think taking unfair advantage of inside information against others is OK. *shrug*

Do not open till Christmas On Christmas, open and post pics Be happy and spread the joy -dZ.

Cute!

Sounds good to me! As for games, I would recommend Christmas Carol sometime during December, but I know that you will kick all of our collective butts on it! -dZ.

The state machine solution doesn't have to be too complicated. Like I said above, it could be as simple as a list of the various obvious states the sprite is in which elicit specialized behaviour, like running, shooting, dead, etc. Then just a bunch of IF/ELSE blocks or an ON GOSUB statement to handle each case. It's a matter of thinking about the sprite as an object reacting to the game world. Personally, I prefer to do this for animations, since depending in certain conditions you may want to switch the animation sequence. The key point is to realize that in such cases, the sprite can only be in a single state at a time (e.g., it can be either Running or Walking or Shooting or AtRest) and therefore the state can tell you which animation sequence to use. (This only applies to the state related to animation only. If the sprite is Shooting while Running, which animation sequence do you want to use? You can't use both at once, so you obviously must pick one. Thus your sprite will only be in one state.) Of course, state machines are very powerful and can be used in many aspects of a game and can get very complex. However, it should be simple for animation engines to reason through and to implement. dZ.

Great!

You shouldn't need to do anything more. The INTYNEW command does only that: create a folder in the Projects folder and a stub file with the same name. So that is fine on your end. I think it's like nanochess said, that the code copied from the forum may contain some strange characters. nanochess, how feasible is it to enhance the compiler to clean up white-space by itself or to beige resilient to these sort of thing? dZ.

With the SDK you don't need the path to "constants.bas". It will add the "lib" folder automatically to the library path during compilation. So the first thing to do is to change that line to: INCLUDE "constants.bas" Also, if the compiler fails, the assembler will not be run -- as long as it returns an error code to STDERR. Otherwise, who can tell what is the return status? Blair, how are you compiling the code and how did you create the project for it in the SDK? dZ.

Congratulations! That's the right attitude to take. I imagine that you are now probably in business with Intellivision Productions, which caused your change of heart. Your earlier conversion projects didn't seem too bothered about pesky copyrights. Good job! -dZ.