Cherry.lua

Cherry is a starter for CoronaSDK App to help building your game.

• Introduction
• Usage
• Libraries
• Starters
• Components
• Music and Sounds
• License
• Third Parties
• Games using Cherry

Introduction to Cherry

You may extend Cherry framework, or just pick few components, in order to start your own game.

Using Cherry

• clone Cherry next to your project, and symlink the lib to your project root: ln -s ../Cherry/cherry cherry
• add a main.lua with

-- main.lua
require 'cherry.main'
require 'src.app'

• add a src/app.lua
• then call App.start() with your options

-- src/app.lua
App:start({
  name    = 'YourGame',
  version = '1.0',
})

• add a env/development.json

{
    "silent": true,
    "invincible": true,
    "view-testing": "playground"
}

see env settings for more options.

A typical tree should be :

├── Cherry
│   ├── cherry
│   │   ├── assets
│   │   │   ├── images
│   │   │   └── sounds
│   │   ├── core
│   │   ├── components
│   │   ├── engine
│   │   ├── libs
│   │   └── screens
│   └── test
│  
├── YourGame
│   ├── cherry -> ../Cherry/cherry
│   ├── assets
│   │   ├── images
│   │   └── sounds
│   │  
│   ├── build.settings
│   ├── config.lua
│   ├── env
│   ├── src
│   │   ├── components
│   │   ├── extensions
│   │   ├── models
│   │   └── screens
│   ├── test
│   └── main.lua

Tests

UT with busted: http://olivinelabs.com/busted/ use luarocks to install busted and luacov

> ./test/run
●●●●●●●●●●●●
12 successes / 0 failures / 0 errors / 0 pending : 0.014314 seconds

Usage

Adding a new Screen

A Screen implements the Composer library.

• Start by creating a new screen, for instance duplicate the simplest one src/screens/Playground.lua
• Register your new screen in the Router : YOUR_NEW_SCREEN = 'YourNewScreen'
• Now you can open your screen from anywhere calling : Router:open(Router.YOUR_NEW_SCREEN)

Adding a new Model

• Each model should implement new and show functions, for instance read how Item is built.
• Register your model in main.lua : YourModel = require 'game.models.YourModel'
• Use YourModel:new() during the LevelDrawer parsing
• Use YourModel:show() during the Game rendering

Components

Either use these components within the full workflow or pick them one by one to use it in your own game.

See documentation for the complete components list and options.

Libraries

See documentation for the complete components list and options.

Tools

• screen routing
• game Camera
• touch controller
• sound library (music + effects)
• an API to register effects from CBEffects.
• user profile and game status
• google analytics events (a lot are already plugged in the workflow)

Music and Sounds

Courtesy of VelvetCoffee, you may use the samples from /assets/sounds for your own game, providing you credit VelvetCoffee for the work and link to :

https://soundcloud.com/velvetcoffee

BSD License

You may use Cherry or a part of it in a free or commercial game or app, providing you follow the BSD crediting requirements, provided in the project LICENSE

Third Parties

• Cherry uses the awesome particle effects provided by CBEffects.
• There are some adapted functions from Underscore.Lua
• Mobile GUI assets from GraphicBurger
• Avatars from Tiny Speck
• Profile icon designed by Miguel C Balandrano

Games using Cherry

• Phantoms released on November 2015 as the actual source for

[todo] Doc to provide

waiting for the doc, read the code

• Look in app.App to see what you may override with App:start(options)
• Look in engine.Game to see what you may override with Game:YourStuff()

core

• env files simple example: development.json

{
    "silent": true,
    "view-testing": "Playground"
}

• adding custom screens
• extending/overriding engine.Game

less important misc

• setting custom bg
• setting custom gravity
• defining colors
• defining analytics ids
• defining facebook ids
• defining ios id