batari Basic publishing requirements?

[DEBRO]

Hi there,

 

Was there once a requirement that any game produced to cartridge that used bB had to reference that fact on the label? It's been a long time so I may not remember correctly.

[Albert]

I've never required a batari BASIC reference on the label or other materials, although a few games have a bB logo somewhere on the label, manual, and/or box.

 

..Al

[RevEng]

There's no requirement to acknowledge bB in any way, in the bB license. There was a discussion on bB mandatory logo/disclosure some years ago. Fred believes it's the programmer's choice.

 

My own feeling is that a homebrewer should always credit non-trivial parts of their final work that aren't entirely their own. bB has tons of utility functions, and IMO it and Fred should be credited somewhere. To do otherwise is passing off someone else's work as your own.

 

A related thread... the official batari basic logo

[Albert]

I agree, and crediting batari BASIC somewhere in the manual, as well as Fred, is good practice. It's not something I'd want to add to the label all the time, though, as I'd prefer to keep the label uncluttered.

 

..Al

[+Gemintronic]

I think in some communities BASIC is looked down upon arbitrarily. In the past sega genesis BASIC compiler users would intentionally eliminate any hint that BASIC was used fearing backlash and poor sales.

 

On an Atari 2600 game space is a legitimate issue. It's really tough to put two title screens into the same game. Instead of having a bB logo I actively show that the game was made in it. I usually leave a project topic with source and ROM. I figure this was it PROVES that one can make a great 2600 game. batari BASIC and the AtariAge community make sure all it takes is a dream and elbow grease.

[RevEng]

I think in some communities BASIC is looked down upon arbitrarily. In the past sega genesis BASIC compiler users would intentionally eliminate any hint that BASIC was used fearing backlash and poor sales.

 

On an Atari 2600 game space is a legitimate issue. It's really tough to put two title screens into the same game. Instead of having a bB logo I actively show that the game was made in it. I usually leave a project topic with source and ROM. I figure this was it PROVES that one can make a great 2600 game. batari BASIC and the AtariAge community make sure all it takes is a dream and elbow grease.

:thumbsup: Totally agree that community support is a big part of it too. People should give back to the community by directing a small amount of attention to bB, instead of just using bB and hoping people assume you made the game from assembly. I look at the good publicity that Princess Rescue brought to bB, and it makes me glad that Sprybug is an upstanding guy.

 

Given the constraints, I don't think a logo has to be in the game or on the label. I actually think it clutters the label, and often ROM is too precious or the screen too cluttered. I put a bB logo in the title screen scroller in 21 Blue, but wouldn't have done it if I had more features to add. If there's a manual for the game, it's a no-brainer to mention it in credits. Implicit credit in AA threads is good too.

[Mr SQL]

IMO you shouldn't have to credit BASIC anymore than a Macro Compiler because it's esentially the same thing unless your coding asm without macro script.

 

I agree with batari and encourage anyone to use bB or the new BASIC Programming to write awesome games and to give the credit where it is really due, to the author of the game. BASIC, didn't write Princess Rescue.