I usually find in a week I have a bare bones of an idea, needing another week to flesh it out.
The reason I suggested three weeks is so that if needed, you could spend that week for a break, or you could work on it, it's more of an "open" week.
The downside to having more weeks involved is that the art showcased then gets diluted - and really, the reason why I'd like to do these jams is to show off the OGA assets produced for them - show love to the artists by using them. And usually, the more assets that are used, reduces the visibility of them.
Also, I am open to whether source code is provided or not.
Some people who might do these jams may decide to crack on with an idea into the commercial realm, in which case, I cannot blame them for withholding source code as it's their bread and butter.
Others might be embarassed about their code - this is a jam after all, and throwing code together haphazardly is natural as the aim is a working product rather than neatness.
Of course, opening your code up does allow for other to learn, or maybe even port at a later date.
Either way, I would just prefer the option being available to people if they want to share their code.
itch.io looks to be a perfect fit for a jams - especially as it has a place for hosting your own jams, and it allows for seemingly all platforms. The only thing I can't see is a place for sharing your code, but that could be a link which I assume you can provide if you desired.
The only thing is that I don't know how much managing you have to do manually - I don't think anyone wants to spend more time than necessary on managing these, especially as the jam will be rolling. Does anyone have a clue what's involved with jams on itch.io?
What do you guys think about time lines? Keeping in mind that we would be talking about a rolling jam to show case the previous art jams. A week, I think, is way to short for a repeating jam, however 2 or 3 weeks seems like an ideal time frame for a quick idea, along with avoiding burning yourself out. I'm also leaning towards a rolling 3 week time frame for this.
I agree with the idea of a coding challenge... it should go hand in hand with the art challenge, where a game or demo is to be made with purely OGA assets, but in particular, the entries *have* to use the entries of the art submitted for the challenge.
I'm also aware of the time required in develloping stuff... so how about a coding challenge, bi/tri-weekly, that is required to use the previous two/three weeks of art challenges (at least one used per art challenge)?
There is another side to this - artists who have submitted art could potentially miss out on having their art used. To try and avoid this, I suggest developers to "claim" it by posting that they are going to use it in the challenge, and you get bonus points for being a unique user of those assets.
One last thing... coding isn't really a focus on this site... should coding challenges be on another site that works with OGA or would the powers here be okay with the challenges being set up and run from here?
The Procedural Death Jam is dear to me as happened a few weeks after I'd found the site, was the motivator that really got me to properly hunt through the site and discover what a treasure trove of art the site really is.
Ever since, this has become one of my staple must visit sites each day.
But, alas, I must agree with you - the old competitions should be archived - heck, all competitions should be in their own sub section.
This is a problem with the web trying to convert word processor generated HTML.
The solution is to copy and paste it into Notepad and then copy from Notepad into the comment box - all your issues will go away.
I usually find in a week I have a bare bones of an idea, needing another week to flesh it out.
The reason I suggested three weeks is so that if needed, you could spend that week for a break, or you could work on it, it's more of an "open" week.
The downside to having more weeks involved is that the art showcased then gets diluted - and really, the reason why I'd like to do these jams is to show off the OGA assets produced for them - show love to the artists by using them. And usually, the more assets that are used, reduces the visibility of them.
Also, I am open to whether source code is provided or not.
Some people who might do these jams may decide to crack on with an idea into the commercial realm, in which case, I cannot blame them for withholding source code as it's their bread and butter.
Others might be embarassed about their code - this is a jam after all, and throwing code together haphazardly is natural as the aim is a working product rather than neatness.
Of course, opening your code up does allow for other to learn, or maybe even port at a later date.
Either way, I would just prefer the option being available to people if they want to share their code.
itch.io looks to be a perfect fit for a jams - especially as it has a place for hosting your own jams, and it allows for seemingly all platforms. The only thing I can't see is a place for sharing your code, but that could be a link which I assume you can provide if you desired.
The only thing is that I don't know how much managing you have to do manually - I don't think anyone wants to spend more time than necessary on managing these, especially as the jam will be rolling. Does anyone have a clue what's involved with jams on itch.io?
What do you guys think about time lines? Keeping in mind that we would be talking about a rolling jam to show case the previous art jams. A week, I think, is way to short for a repeating jam, however 2 or 3 weeks seems like an ideal time frame for a quick idea, along with avoiding burning yourself out. I'm also leaning towards a rolling 3 week time frame for this.
I agree with the idea of a coding challenge... it should go hand in hand with the art challenge, where a game or demo is to be made with purely OGA assets, but in particular, the entries *have* to use the entries of the art submitted for the challenge.
I'm also aware of the time required in develloping stuff... so how about a coding challenge, bi/tri-weekly, that is required to use the previous two/three weeks of art challenges (at least one used per art challenge)?
There is another side to this - artists who have submitted art could potentially miss out on having their art used. To try and avoid this, I suggest developers to "claim" it by posting that they are going to use it in the challenge, and you get bonus points for being a unique user of those assets.
One last thing... coding isn't really a focus on this site... should coding challenges be on another site that works with OGA or would the powers here be okay with the challenges being set up and run from here?
Yes, they will blow up any nearby presents... and blown up presents don't count as collected!
That makes it more difficult for you to get a perfect score ^_^
I don't think there is anything here - I've done a search for "head" as well as "health" and gone through every page.
Oh well, not to worry, I'll do something that isn't a head.
The Procedural Death Jam is dear to me as happened a few weeks after I'd found the site, was the motivator that really got me to properly hunt through the site and discover what a treasure trove of art the site really is.
Ever since, this has become one of my staple must visit sites each day.
But, alas, I must agree with you - the old competitions should be archived - heck, all competitions should be in their own sub section.
The website in your attribution doesn't work for me - does the website address need to be updated before I can use these?
Did the 32 bit version work for you William?
I think I have found the problem - my own stupidity:
I uploaded a 64bit version, so anyone using a 32 bit OS... it isn't going to work.
So, I've now posted a 32 bit version. Nothing has changed content or codewise, just the compilation.
Pages