"CC0? No way. This is a lot of high quality stuff, you deserve credit at the very least."
Hopefully most users will give the author credit as a courtesy at least. I know in my unreleased project I keep a credits file that doesn't distinguish between OGA-BY and CC0. If I ever release a beta I'll credit OGA and point to the credits file at a minimum. (Though, as a note to developers, keeps your credits file up to date as you go.)
"There's a collections page for 8x8 rogues assets here, but keep in mind that the rest are different colors, often different licenses, and many times not actually 8x8 tiles. They might prove useful, though: http://opengameart.org/content/8x8cc0oga-byroguelike"
The funny thing is that I've been plucking away at a rouguelike for a long time, hence the reason for maintaining the above collection, and I've been normalising everything to DB32. So many thanks to you and SpiderDave as this was like mana from heaven. It's great!
The reason for the CC0 and OGA-By in that collection is that I intend to treat all of the graphics in the roguelike I'm working on as OGA-By (to preserve my ability to get into various app stores) so anything with a stronger copyleft would be problematic (AFAIK).
edit: This collection was never intended to be public (more 'stuff I might use'), but it's attracted favorites. Since it has, I sorted out the credits file in my project, then cleaned up the collection (where I also found 1 entry that was CC-By) of things that couldn't be easily bodged into an 8x8 game, bits of interfece, etc. I then set it to public. Given my own slow rate of progress I imagine it will be updated well into the future.
As somebody that does use the tags these ideas sound good to me. The order of priority in the bullet point list sounds good, but I'd move the last two items up the list by a couple, or few, places.
Case ignoring seems like a good idea, as would be testing for, or just plain stripping, spaces, hypens, and underscores, and then testing if a tag is unique. 8bit, 8Bit, 8BIT, 8-bit, 8-Bit, 8-BIT, 8 bit, 8 Bit, 8 BIT, 8_bit, 8_Bit, and 8_BIT should probabl all be the same tag. (Not that all of the above tags exist, but they could, and probably shouldn't.)
I just want to say that I love your art. I'm actually using your roguelike set in a python / pygame roguelike that would be open source, and may or may not ever make it off my harddisk. I've been plucking away at it forever. I actually have a bunch of your stuff in this CC0 and OGA-BY art collection to help with that task:
Awesome, I added them to:
http://opengameart.org/content/8x8cc0oga-byroguelike
"CC0? No way. This is a lot of high quality stuff, you deserve credit at the very least."
Hopefully most users will give the author credit as a courtesy at least. I know in my unreleased project I keep a credits file that doesn't distinguish between OGA-BY and CC0. If I ever release a beta I'll credit OGA and point to the credits file at a minimum. (Though, as a note to developers, keeps your credits file up to date as you go.)
Somebody is using this for: '8 bit live wallpaper' in the Google Play store. I noticed the art as soon as a saw it. Seems neat.
These are great assets.
"There's a collections page for 8x8 rogues assets here, but keep in mind that the rest are different colors, often different licenses, and many times not actually 8x8 tiles. They might prove useful, though: http://opengameart.org/content/8x8cc0oga-byroguelike"
The funny thing is that I've been plucking away at a rouguelike for a long time, hence the reason for maintaining the above collection, and I've been normalising everything to DB32. So many thanks to you and SpiderDave as this was like mana from heaven. It's great!
The reason for the CC0 and OGA-By in that collection is that I intend to treat all of the graphics in the roguelike I'm working on as OGA-By (to preserve my ability to get into various app stores) so anything with a stronger copyleft would be problematic (AFAIK).
edit: This collection was never intended to be public (more 'stuff I might use'), but it's attracted favorites. Since it has, I sorted out the credits file in my project, then cleaned up the collection (where I also found 1 entry that was CC-By) of things that couldn't be easily bodged into an 8x8 game, bits of interfece, etc. I then set it to public. Given my own slow rate of progress I imagine it will be updated well into the future.
As somebody that does use the tags these ideas sound good to me. The order of priority in the bullet point list sounds good, but I'd move the last two items up the list by a couple, or few, places.
Case ignoring seems like a good idea, as would be testing for, or just plain stripping, spaces, hypens, and underscores, and then testing if a tag is unique. 8bit, 8Bit, 8BIT, 8-bit, 8-Bit, 8-BIT, 8 bit, 8 Bit, 8 BIT, 8_bit, 8_Bit, and 8_BIT should probabl all be the same tag. (Not that all of the above tags exist, but they could, and probably shouldn't.)
More great work...
I just want to say, more nice work, awesome!
I just want to say that I love your art. I'm actually using your roguelike set in a python / pygame roguelike that would be open source, and may or may not ever make it off my harddisk. I've been plucking away at it forever. I actually have a bunch of your stuff in this CC0 and OGA-BY art collection to help with that task:
http://opengameart.org/content/8x8cc0oga-byroguelike
I don't have any specific ask, well, other than keep on being awsome!
Here's a screen shot:
Nice! (Along with the torch guy.)
Pages