That is actually an issue that has gone unaddressed for a while. The attribution was not properly tracked for several iterations of those LPC generators. However, by remarkable coincidence, Bluecarrot (along with Castelonia and others) have just recently began efforts to address the very problem you've come across. See the this post for more information: https://opengameart.org/forumtopic/lpc-spritesheetcharacter-generator-at...
Oh, well. Glad you've found it! :) I hope you'll give it a go. I'm glad you've been adding the animated preview to all your spritesheets, but I have to be honest, the gifs generated by the Chasys Draw IES Artist program don't fully do them justice.
Ah, well I'm not sure I did fix it. I'm guessing that same method would still fail. I went to the submission page and clicked "add to collection" on the left pane.
I was able to add it just fine. What are the steps you're using to try to add it. I mean, you can't add it now that it's already added, but let me know if you need me to remove it so you can test it again.
I fully support this effort. I am willing to contribute as well, but - as bluecarrot hinted at - this is one of those projects where more help might mean more work. As they say in my line of work: "what one programmer can accomplish in one month, TWO programmers can accomplish in just two months." Any help given should be at the direction of bluecarrot, to be sure the work is consistent and effective.
I do not agree with the notion that the full scope of attribution for all the LPC works is just too unwieldy. If the credits.csv ultimately has 2000 rows, that is a lot, sure, but hardly 100 pages long. Any developer must necessarily add at least one line of code to his/her project per sprite sheet or LPC asset they want to use. Adding thousands of lines of code that reference and import the artwork is no big deal, but adding (at most) the same amount of text to a credit file for all that free stuff is just too hard? I don't buy it.
I realize that isn't really the point of what was being said. It is true that the attribution for all the LPC content is complicated and cumbersome, but having insufficient or incomplete credit is no alternative. From what I understand from the suggestions above, the idea is to have:
A comprehensive spreadsheet with the full attribution: filename, title, author, license, url... That can be either dropped in whole to a project that uses any one or more (or all!) LPC assets... OR easily paired down by the developer as they do a simple check-all-that-apply, including rows for any LPC assets they're using, excluding rows for assets they are not using.
Code added to the popular LPC character generators that automatically build a credits file. As components are added to (or removed from) the character, the generator adds (or removes) the corresponding attribution text to a running list.
I realize it may be difficult for I or others to effectively directly contribute to this heroic effort, so I'm thinking of posting a bounty for its progress. What do you think of $0.10 for every row (asset) completed on that .CSV? I know that isn't much, but hopefully it will help take the sting off of how monotonous this task can be at times. I'll have to come up with a few limits to make sure y'all don't make me homeless, but is it worth considering? Would it help keep motivation strong?
If your script is smart enough to grab the asset itself from archive.org, why couldn't it also grab the license for that asset? they're listed together, and there are even script-generated licensing info files available for any asset you download. Regardless, the following may be a more desireable solution:
Sys admin says if you feel like making a drupal module that auto-creates any new submissions into a github repo, he'd allow that. From there you could script download and/or pull the entire archive of OGA assets from github.
That is actually an issue that has gone unaddressed for a while. The attribution was not properly tracked for several iterations of those LPC generators. However, by remarkable coincidence, Bluecarrot (along with Castelonia and others) have just recently began efforts to address the very problem you've come across. See the this post for more information: https://opengameart.org/forumtopic/lpc-spritesheetcharacter-generator-at...
Did it not alert you when I posted this comment? https://opengameart.org/comment/88683#comment-88683
Oh, well. Glad you've found it! :) I hope you'll give it a go. I'm glad you've been adding the animated preview to all your spritesheets, but I have to be honest, the gifs generated by the Chasys Draw IES Artist program don't fully do them justice.
Ah, well I'm not sure I did fix it. I'm guessing that same method would still fail. I went to the submission page and clicked "add to collection" on the left pane.
That could work. Please pm me when you plan on using it so I can make sure it isn't getting too close to hindering site performance.
Could be. What steps wet you taking to add it?
I was able to add it just fine. What are the steps you're using to try to add it. I mean, you can't add it now that it's already added, but let me know if you need me to remove it so you can test it again.
I fully support this effort. I am willing to contribute as well, but - as bluecarrot hinted at - this is one of those projects where more help might mean more work. As they say in my line of work: "what one programmer can accomplish in one month, TWO programmers can accomplish in just two months." Any help given should be at the direction of bluecarrot, to be sure the work is consistent and effective.
I do not agree with the notion that the full scope of attribution for all the LPC works is just too unwieldy. If the credits.csv ultimately has 2000 rows, that is a lot, sure, but hardly 100 pages long. Any developer must necessarily add at least one line of code to his/her project per sprite sheet or LPC asset they want to use. Adding thousands of lines of code that reference and import the artwork is no big deal, but adding (at most) the same amount of text to a credit file for all that free stuff is just too hard? I don't buy it.
I realize that isn't really the point of what was being said. It is true that the attribution for all the LPC content is complicated and cumbersome, but having insufficient or incomplete credit is no alternative. From what I understand from the suggestions above, the idea is to have:
I realize it may be difficult for I or others to effectively directly contribute to this heroic effort, so I'm thinking of posting a bounty for its progress. What do you think of $0.10 for every row (asset) completed on that .CSV? I know that isn't much, but hopefully it will help take the sting off of how monotonous this task can be at times. I'll have to come up with a few limits to make sure y'all don't make me homeless, but is it worth considering? Would it help keep motivation strong?
If your script is smart enough to grab the asset itself from archive.org, why couldn't it also grab the license for that asset? they're listed together, and there are even script-generated licensing info files available for any asset you download. Regardless, the following may be a more desireable solution:
Sys admin says if you feel like making a drupal module that auto-creates any new submissions into a github repo, he'd allow that. From there you could script download and/or pull the entire archive of OGA assets from github.
I'll ask the host about a backup for you, but your guess about an IP ban is correct.
I have done that exact same thing, so when I saw this thread I was thinking "wait, maybe there IS a bug!"
Pages