1. Macros:

Some variables for UI and drawing

__gamescale__ : double A handy double that represents the default size of anything drawn

btn_a : bool Will be true when button a is pressed

btn_b : bool    Will be true when button b is pressed

btn_d : bool   Will be true when the down button is pressed

btn_u : bool   Will be true when the up button is pressed

 btn_l : bool Will be true when the left button is pressed

btn_r : bool   Will be true when the right button is pressed

2. Colors:

Colors are represented as numbers. They wrap so 17 = 0, 18 = 1 etc

0 Transparent

1 Black

2 Dark Grey

3 Light Grey

4 White

5 Beige

6 Hot Pink

7 Red

8 Burgundy

9 Brown

10 Orange

11 Yellow

12 Light Green

13 Dark Green

14 Light Blue

15 Violet

16 Dark Blue

3. Callbacks:

Functions that you can override to make your game

_init() 

Called once at the start of program execution

_draw() 

Called 30 times per second, safe place to call graphic methods

_update() 

Called 30 times per second, safe place to respond to input (btn_l, btn_r etc.)

4. Draw Methods:

Functions that draw things to the game screen when you hit play

rectifll(x1: double, y1: double, x2: double, y2: double, color: double)

Draw a filled rectangle with x1:y1 being the top left corner and x2:y2 being the bottom right corner. Refer to Colors

log(text: String, x: double, y: double,  color: double)

Write some text at a given point and with the requested color

cls() 

Clear the screen to black

cls(color: number) 

Clear the screen to a given color

sprite(no: double, x: double, y: double) 

Draws a sprite at the given coordinates. Sprite numbers can be seen in the sprite editor between the sprite display windows and the sprite editor window

sprite(no: double, x: double,y: double,scale: double)

 Same as above, but with optional scale parameter. Default is 4 (based on __gamescale__ constant)

sprite(no: double, x: double, y: double, scale: double,flip: bool) 

Same as above, but with optional flip param. True is flipped, false is not.

sprite(no: double, x: double, y: double, scale: double, flip: bool, rotation: double) 

Same as above but with 90 degree rotation increments (1 = 90, 2 = 180, 3 = 270, 0 = 360). Thiw will wrap automatically to the modulus of these 4 values

map(celx: double, cely: double, sx: double, sy: double, celw: double, celh: double)

Draw a segment of map from the map editor. celx:cely (from x, from y) the top left corner of the map to draw from. celw:cely the width and height of the map segment ti drawo, abd. sx:sy the position where the top left corner of the map will be drawn from

drawmap(fX: double, fY: double, tX: double, tY: double, x: double, y: double)

 Draw a segment of map from the map editor. fX:fY (from x, from y) the top left corner of the map to draw from. tx:ty (to x, to y) the bottom right corner to draw too. x:y the top left corner of the screen that the map will be drawn from

5. Game Logic Methods:

Things I'm working on to make development easier

mget(x: double, y: double): double

Get the tile at a given position on the map.

areacontains(x: double, y: double, w: double, h: double, tile: double): bool

Query a rectangular segment of the map to see if it contains a given tile number. A clunky helper method for collision detection.  Let me know how I can simplify this!!!

5. Debug methods

Handy methods for sanity checking all that spaghetti code

hlog(text: String)         

Outputs text to a scrollable debug text area that overlays the game display

alert(text: String)          

Throws up an alert dialog with some text and stops execution on the frame the alert was triggered on

hassert(result: bool, message: String) 

 Outputs either "Test Passed: " + message or "Test Failed: " + message to the debug text area. It was more for me to test things, but I left it in just in case someone needs it!

6. Pages