diff options
Diffstat (limited to 'templates/api/jam2026.html')
| -rw-r--r-- | templates/api/jam2026.html | 121 |
1 files changed, 121 insertions, 0 deletions
diff --git a/templates/api/jam2026.html b/templates/api/jam2026.html new file mode 100644 index 0000000..78ae617 --- /dev/null +++ b/templates/api/jam2026.html @@ -0,0 +1,121 @@ +<!DOCTYPE html> +<html lang="en"> + <head> + <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no"> + <title>LCOLONQ MICROJAM 2K26-A-PALOOZA</title> + <link rel="icon" href="/assets/images/mrgreen.png"> + <link rel="stylesheet" type="text/css" href="/assets/css/shared.css"> + <link rel="stylesheet" type="text/css" href="/assets/css/jam.css"> + </head> + <body id="lcolonq-jam"> + <h1>LCOLONQ MICROJAM 2K26-A-PALOOZA</h1> + <div id="lcolonq-jam-content"> + <ul> + <li><b>what is it</b>: a game jam for <a href="https://colonq.computer">the LCOLONQ zone</a> or <a class="lcolonq-green" href="https://greencircle.live">"greencircle"</a> or cyberspace or whatever else we call it!</li> + <li><b>why is it</b>: let's have some fun on the computer together!</li> + <li><b>when is it</b>: submissions are due on <b>Friday, July 17th 2026</b>.</li> + <li><b>where is it</b>: submit links to entries on Discord or IRC or Twitch Chatroom or anywhere we are likely to see them. if you need a place to upload your submission, contact clonk! this is a small group, we can ask each other questions and figure things out together. + <li><b>who is it</b>: you, maybe! if you don't feel confident making a game alone, maybe team up with somebody else! ask around in the Discord or IRC or Twitch Chatroom or anywhere else!</li> + <li><b>how is it</b>: pretty good; see below! + </ul> + <h2 id="lcolonq-jam-details">THE DETAILS</h2> + <div class="lcolonq-jam-subtitle">or, what are we making, actually</div> + <div id="lcolonq-jam-details-body"> + <p> + For this event, your challenge is to make a "microgame". + Microgame is a term used by the <a href="https://en.wikipedia.org/wiki/WarioWare">WarioWare</a> game series to describe short, (mostly) self-contained minigames played in rapid succession. + The individual microgames tend to present a single gameplay mechanic or task for the player to perform, with a well-defined success and failure state. + Typical microgames are only a few seconds long, while some end-of-stage "boss games" can last a minute or more. + In WarioWare, the player is presented with a series of microgames to play in a random order. + Failing at an individual microgame costs the player a life, and losing all lives means game over! + </p> + <p> + For an example of this type of gameplay, <a href="https://youtu.be/h_cQWl_drqg?t=344">here is a nice demonstration video</a>. + </p> + <p> + Your mission in this game jam is to make a microgame! + At the end, we'll collect all the submissions together, so you can play through the whole collection like you would a stage in WarioWare. + In order for this to work nicely, it's best if everyone follows some simple guidelines. + These mostly aren't hard-and-fast rules, but moreso a framework to ensure that the overall collection is playable. + </p> + <ol> + <li> + <h4>Make a game that's playable in the browser.</h4> + <p> + The browser is how we're going to ensure all of the games can play nicely together. + This doesn't mean you have to write a game with JavaScript! + </p> + <p> + Many languages and libraries can be built to WebAssembly. For example, if you like C and <a href="https://www.raylib.com/">raylib</a>, check out <a href="https://github.com/raysan5/raylib/wiki/Working-for-Web-%28HTML5%29">this guide</a>! It's also quite easy to write Rust programs targeting WebAssembly. In general, if you have a preferred language and graphics library, it's likely you'll be able to make something work! + </p> + <p> + Full-fledged game engines like Godot also have the ability to export a web build. For Godot, see <a href="https://docs.godotengine.org/en/stable/tutorials/export/exporting_for_web.html">the documentation</a>. + </p> + <p> + It's also perfectly fine to work with JavaScript and Canvas, either using some library or plain browser APIs! If you'd like to go this route and aren't sure where to start, check out the MDN documentation for <a href="https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API">the Canvas API</a> or maybe <a href="https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API">WebGL</a>. If you'd like something a bit more batteries-included, maybe check out <a href="https://github.com/pixijs/pixijs">Pixi</a> or <a href="https://github.com/phaserjs/phaser">Phaser</a>. + </p> + </li> + <li> + <h4>Games should be primarily controlled using the mouse.</h4> + <p> + We want to make sure that someone playing the collection doesn't get confused by the controls. + With keyboard controls, each game might pick totally different keys, and adjusting the player will be a challenge. + As such, please center your game's control scheme around a standard two-button mouse. + You're still welcome to use the keyboard and any other input method that's generally available, but try to avoid assuming that the player will know the control scheme you require. + For example, a keyboard-involved microgame might involving mashing keys indiscriminately, or playing a "hot-and-cold" game based on the physical locations of keys pressed in the player's keyboard layout. + Get creative! + </p> + </li> + <li> + <h4>Keep it short and focused! Less than a minute is ideal.</h4> + <p> + Ideally your game is tightly focused on a single gameplay idea. + Feel free to interpret this however you wish! + If you want to make a two minute mini-RPG, be my guest! + Rough and interesting is a good way to go. + </p> + </li> + <li> + <h4>Make sure there is an obvious win condition and lose condition.</h4> + <p> + We need a way to know if the player should lose a life after your game runs. + The player running out of time is a perfectly good lose condition (but make sure to display a timer somewhere onscreen if this is the case!). + But again, feel free to be inventive! + </p> + </li> + </ol> + </div> + <h2 id="lcolonq-jam-rules">THE RULES</h2> + <div class="lcolonq-jam-subtitle">ok these are actual rules don't bend these ones please</div> + <div id="lcolonq-jam-rules-body"> + <ul> + <li> + <p> + Alongside your game, please <b>submit source code</b> (either a link to a repository or actual source in an archive file). Please <b>include the open-source license</b> your are releasing your code under, as well as any licenses and attribution for any assets used. + </p> + </li> + <li> + <p> + Please <b>do not use any "trained" machine learning tool</b> with external training data for programming or asset creation. That is: no off-the-shelf LLMs, image generation, etc. anywhere in the development process or final game. Feel free to use machine learning techniques at your leisure if you're using a model you trained entirely yourself on data you have collected yourself (and to which you have a license). + </p> + <p> + In brief: <b>Claude code/ChatGPT/AI images are banned</b>. If you'd like to write some weird genetic algorithm thing or do reinforcement learning for game AI or procedural textures or whatever else, that's cool and please do it! + </p> + </li> + <li><b>Be kind</b>.</li> + </ul> + </div> + <div id="lcolonq-jam-footer"> + LCOLONQ 2"K"26. Most rights reversed. All words endorsed by my employer. I love the computer and the people on it. + </div> + </div> + <script type="module"> + let body = document.getElementById("lcolonq-jam-details-body"); + let details = document.getElementById("lcolonq-jam-details"); + details.addEventListener("click", () => { + body.classList.toggle("lcolonq-jam-cool"); + }); + </script> + </body> +</html> |