Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make It or Break It (season 1) #220

Wodann opened this issue Jun 11, 2020 · 1 comment

Make It or Break It (season 1) #220

Wodann opened this issue Jun 11, 2020 · 1 comment
good first issue


Copy link

@Wodann Wodann commented Jun 11, 2020

In honour of the Mun v0.2 release we are launching the Make It or Break It contest. We want to invite both content creators and developers to use Mun v0.2 and make or break something with/in Mun.

There are two tracks in which you can participate:

Make It

Mun was designed to empower creation through iteration, by using natively supported hot reloading for data and functions. Even though Mun v0.2 is still lacking language features - such as enums and arrays - and is limited to single source files, we are excited to see what games and apps people come up with. After all, didn't great artists like Monet create their masterpieces by limiting available tools?

For inspiration, have a look at the classic game Pong (Making of video) that Mun Team devs made.

Break It

Mun consists of the Mun ABI1, Mun Compiler1,2,3, and Mun Runtime1,2; each with their own tests. Still, there are a lot of untested code paths and other (non-logical) ways that Mun can crash and 🔥. Can you find the craziest, most unexpected bugs?

For inspiration, have a look at breaking Mun's struct hot reloading or try fuzzing (#152).


A contest wouldn't be a contest if there was no award. At the end of every season (i.e. release cycle), we'll release a poll to our Discord community to determine the most popular Make It or Break It demos. The top contender will be awarded with a mention on our website, but the Mun Team reserves the right to award multiple top contenders (always in order of popularity).

Additionally, all (merged) submissions will be credited on our Rust and C++ example repositories.


You are free to make any number of submissions in both the Make It and/or Break It tracks.

To submit your entry:

  • Make It
    • C++: Create an Issue in the mun-lang/example-cpp repository, linking to your fork of the example-cpp repository. As C++ dependency management can be a little more involved, we might consider creating separate branches or repositories within the mun-lang GitHub organisation for your submission.
    • Rust: Create a Pull Request in the mun-lang/example-rs repository. Your Rust code should go in the examples directory alongside the file, whereas Mun code should be alongside the pong.mun source file in the resources directory.
  • Break It
    • Create an Issue in the mun-lang/mun repository, detailing a #[test] fn your_fn() { .. } or minimal example along with the resulting error message or short video to demonstrate the bug.

Please make sure to reference this issue in your pull request or issue: - so we know it is related to the Make It or Break It contest. Also, make sure to read our contributing guidelines and code of conduct before submitting.

@Wodann Wodann added the good first issue label Jun 11, 2020
@Wodann Wodann added this to the Mun v0.3.0 milestone Jun 11, 2020
@Wodann Wodann added this to 0.3 (Tock) in Roadmap Jul 25, 2020
Copy link
Collaborator Author

@Wodann Wodann commented May 8, 2021

A new release also means the end of our first season of Make It or Break It. Our request for contenders, was answered by a lot of reporters filing bugs in the Break It track, but we only had a single contributor in the Make It track. After some discussion, we decided to skip a poll and instead decide on the - to us - unanimous winner: this Spaceship game created by @legendiguess using Mun & Rust:


@Wodann Wodann closed this as completed May 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
good first issue
0.3 (Tock) (Finished)

No branches or pull requests

2 participants