I think submitting the game as a package should be encouraged - but just tagged as game
I like having both forms of judging: judged and people’s choice
I’d also like the participants to share as much as possible; screenshots of development/sketches stream & record live coding seasons and demos, tweet updates #racketgamejam2019
Probably should also tag racketgamejam2019 in the packages too :slightly_smiling_face:
Good idea.
Agreed on encouraging submitting packages tagged as game. Should it be a requirement? Submitting packages can be intimidating.
Any thoughts on
> I’d also like the participants to share as much as possible; screenshots of development/sketches stream & record live coding seasons and demos, tweet updates #racketgauejam2019
Encouragement sounds good, requirement would be bad I think. Otherwise might make people uncomfortable. I know I’d feel uncomfortable participating in a game jam that required I advertise my participation.
I’d also encourage creating an executable.
We could include instructions for how to use the racket-launcher-names field of the info.rkt file to make the racket package manager automatically set up an executable that runs their game
i.e. you can set up a package mypkg with an info.rkt like this: (define racket-launcher-names (list "mygame" "othergame"))
(define racket-launcher-libraries
;; these paths are relative to this info.rkt file
(list "mygame.rkt" "othergame.rkt")) …and then raco pkg install mypkg will automatically create executables named mygame and othergame that run the code in mypkg/mygame and mypkg/othergame, respectively.
They’re added to the same directory that the racket, drracket, scribble, and raco executables are in so they’ll automatically be on your $PATH too
Maybe a skeleton package?
Ooo, that’s a great idea
Github has template repositories too, that might help
example template repository: https://github.com/jackfirth/racket-package-template