Fable and Bucklescript are similar projects which both use OCAML (F# is based on OCAML) to compile to JavaScript. I ported the OCAML version to F# to compare the two approaches.

MariOCaml is a port of Mahsu's work to the excellent BuckleScript compiler, for the whole game it generates only 7K byte gzipped JS and takes 0.57s to build (including the start up time of npm).

MariOCaml is an HTML 5 canvas web-browser implementation of a well known platformer written exclusively in OCaml.

Windows, Max, Linux - requires .net Core Updated to use Fable with Paket

yarn install 
dotnet restore
dotnet fable npm-run rollup

• 2D Mario platformer that emulates the platformer mechanics of Super Mario Bros.
• Web-based playable implementation with graphics (Ocaml transpiled to javascript).
• Procedural level generator that randomly generates levels.

MariOcaml is an OCaml implementation of Super Mario Bros. The game includes several basic enemies, blocks, and items, with particle support. The underlying system follows a director model, with the director maintaining state based on game objects and tiles, including Mario, items, and obstacles. The implementation of enemies and items is designed to be easily extensible. Furthermore, MariOcaml supports a game-over and game-win states, as well as score and coin counts, emulating several of the core mechanics of Mario.

The design follows a clean, modular, and extensible system to ensure that more features can easily be added. Levels are procedurally generated (pseudo-randomly), algorithmically creating an environment of textures and objects that are interactable. The procedural generation generally generates a playable map, but due to the nature of random generation, maps may not be the most aesthetically appealing. Additionally, the game is interactive and graphical using js_of_ocaml, which enables cross-compiliation of Ocaml to javascript, allowing MariOcaml to be run in any modern web browser.

The underlying procedural generation utilizes a grid system to generate objects, taking account parameters such as proximity and location. During game-play, the director maintains the game state, including the location and status of both items, enemies, and the character.

• Director - The heart of the game, executes the main game loop and performs updates on the map, canvas, and objects. Also executes the side effectual collision detection.
• Viewport - Represents a slice of the game map which is currently in view and rendered on the canvas.
• Procedural Generator - Generates the game level in a game map to be played.
• Actors - Represents the characters, items, and obstacles in the Mario game world.
• Sprite - The visual representation of an object to be drawn on the canvas. Contains the ability to create sprites from a template configuration based on the type of actor.
• Object - The abstract representation of a specific actor on the game map. Contains the ability to create objects from a template configuration based on the type of actor.
• Particle - Represents a non-collidable visually oriented object on the map. This includes destruction and creation effects.
• Draw - Contains methods which update the canvas.

Pull requests fixing bugs, adding functionality, or improving organization are welcome!

MariOCaml was originally conceived for Cornell University's Fall 2015 CS3110 final project.

• Matthew Hsu (@mahsu)
• Ashley Xue (@ashleyxue529)
• Liam Bui (@LiamBui)