You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the sake of potentially rendering the tileset acceptable for future reintroduction into CDDA, I need to maintain a list of all sprites known or suspected to be in violation of any potential liscences.
Jerky, possibly other sprites that might be edited from it (the jerky sprite being from a Minecraft mod is specifically what sparked this).
I need to check whether fruit leather is still derived from it, I could've sworn that during the MShock Modded days I based my fruit leather sprite off whatever jerky was at the time.
Medium blobs, possibly amoebic molds, are suspected to be derived from Dungeon Crawl's jelly sprite.
All animatronic monster sprites are suspected to be downscaled screen captures of FNAF assets rather than original mockups.
PK Doom monster sprites are in an unknown state, sprites appear to be original work (possible small chance of being stolen from DoomRL, will need to check for myself), but may hue closely enough to be a concern.
Evidently the infamous jerky was traced all the way back pre-MShock, to a set known as Raga. We will have to look through its content and pick through the sprites to replace everything from that tileset, as this is the specific source that's going to poison the entire MShock lineage.
Zucchini, garlic, hickory root have been confirmed suspects as well. This is worrying, as those last two at minimum are items that predate base MShock set.
The text was updated successfully, but these errors were encountered:
Depending on what the verdict is regarding whether CDDA's use of those sprites is acceptable or not, this will either help us vet or eliminate a large chunk of more recent work.
For the sake of potentially rendering the tileset acceptable for future reintroduction into CDDA, I need to maintain a list of all sprites known or suspected to be in violation of any potential liscences.
The text was updated successfully, but these errors were encountered: