Submit to the bot using the !submit [url] command, where
[url] is the link to the jam submission page for
your jam game. This is the one like https://itch.io/jam/[jam
name]/rate/[numbers You can submit to the Twitch or Discord bot, but Twitch bot
submissions get higher priority.
Note you can only submit while the bot is running and I'm live streaming. Check the Jam Games page to see the stream and bot status. If both are online, you will also see a message saying "Accepting games from [list of jams]."
You are limited to one submission at a time, so if there are multiple jams or you have multiple entries, you won't be able to submit again until I play your current submission.
Usually, there will be a limited number of jams for which Josh is
accepting submissions. You can check with the !jams command
or on the Jam
Games page.
Games from Twitch subscribers are played first, then Twitch submissions, then Discord submissions. Each is on a first-come, first-serve basis. Because of the rank/priority system, your game may get bumped by a later submission.
You can check your queue position with the !check command
once per hour. If you overuse this command, you will be banned
from using it further.
If the queue is light, I won't impose a hard limit and will stop when 1) I've completed all the apparent content for the game, 2) I've run out of things to say about the game, 3) I am no longer able to progress in the game. Generally, I'll try to go at least 10-15 minutes, but some jam games are significantly shorter or simpler than that target.
If there's a big backlog, I may institute a hard limit of 10 or 15 minutes per game, depending on the size of the queue. Note this is an upper limit so you're still not guaranteed a minimum amount of time played.
In addition to a VOD recording on his Twitch channel, Josh will post a permanent version on his YouTube channel that you can access at any time.
It's also on Josh's endless TODO list to add a list of reviewed jam games with links to the relevant YouTube video and timestamp.
If the queue is long, I may decide to skip submitters who aren't in the stream chat so he can prioritize live feedback.
My perspective for feedback starts with the thought: "If I had made this prototype and wanted to build it into a full commercial release, what would I feel needs to change?"
I'm >one gamer with one opinion, and I might not even be your target audience. I like platformers, shooters, and RPGs more than RTS or obtuse puzzle games. Not because they're better, but because that's my taste. If you hand me a game I don't like, I'll try to be objective with my feedback, and as kind as I can, but I refuse to be disingenuous.
You don't have to listen to my feedback, either. It's your game, not mine. You should get as much feedback as you possibly can and cherry-pick the changes that best suit your vision, if you move ahead with the game.
Try your damndest not to say anything. It's super difficult, but this is the best way to get pure, honest, useful feedback. Watch and litsen carefully, take notes, and save any questions or comments for *after* I finish playing your game.
If you guide my feedback with "You're supposed to do X" and "I didn't want players to do Y" then you'll never know how a player would experience your game without you in the room. Imagine Shigeru Miyamoto leaning over your shoulder, pointing out that you missed a mushroom block and should go back to get it. Would that be fun?