-
Notifications
You must be signed in to change notification settings - Fork 0
Prelude
Before any sections of the script is declared you have the space at the top for settings and game infomation.
title [string example: "My Amazing Game"]
The name of your game. Appears on the title screen.
author [string]
Your name goes here. This will appear in the title screen of the game.
color_palette [int/key]
By default, when you use colour names, they are pulled from a variation of Arne's 16-Colour palette (carried over from the original PuzzleScript). However, there are other palettes to choose from:
- mastersystem
- gameboycolour
- amiga
- arnecolors
- famicom
- atari
- pastel
- ega
- amstrad
- proteus_mellow
- proteus_rich
- proteus_night
- c64
- whitingjp
(you can also refer to them by their numerical index) (these might change in the future)
again_interval [float]
The amount of time it takes an 'again' event to trigger..
background_color [Color/Hex]
Can accept a color name or hex code (in the form #412bbc). Controls the background color of title/message screens, as well as the background color of the website. Text_color is its sibling.
Text_color [Color/Hex]
Can accept a color name or hex code (in the form #412bbc). Controls the font color of title/message screens, as well as the font color in the website. Background_color is its sibling.
debug
This outputs the compiled instructions whenever you build your file. For instance, the line
[ > Player | Crate ] -> [ > Player | > Crate ]
is compiled into four instructions, as the output from debug shows:
Rule Assembly : (4 rules )
===========
(52) UP [ up player | crate ] -> [ up player | up crate ]
(52) DOWN [ down player | crate ] -> [ down player | down crate ]
(52) LEFT [ left player | crate ] -> [ left player | left crate ]
(52) RIGHT [ right player | crate ] -> [ right player | right crate ]
===========
the number on the far left is the group number of the disassembled - based on the line-number of the rules. The compilation step removes all relative directions ( ^, v, <, and >), and replaces them with UP, DOWN, LEFT, and RIGHT.
flickscreen [int width]x[int height]
Setting flickscreen divides each level into WxH grids, and zooms the camera in so that the player can only see one at a time - the camera does not follow the player around on a move-to-move basis, but if the player moves from one part of this grid to another, the camera flicks to the new position.
homepage [string: example "www.mypage.com"]
The homepage of the author. This doesn't appear directly in the game itself, but is included in the exported HTML build. (might get replaced)
key_repeat_interval [float]
When you hold down a key, how long is the delay between repeated presses getting sent to the game (in seconds?).
noaction
Hides the action key (X) instruction from the title screen, and does not respond when the player pressed it (outside of menus and cutscenes and the like).
norepeat_action
For many games, you don't want holding action down to retrigger it - games where you're toggling a switch, say. For these games, set norepeat_action, and the action button will only respond to individual presses.
noundo
Disables the undo key (Z)
norestart
Disables the restart key (R)
realtime_interval [float]
Disables the restart key (R)
require_player_movement
This is a common requirement in games - if the player doesn't move, cancel the whole move. This is equivalent, where there's only one player character, to the following:
[Player]->[Player Temp]
late [ Player Temp ] -> CANCEL
late [ Temp ] -> [ ]
run_rules_on_level_start
For some games, you will want, before the player sees the level, for the rules to be applied once.
scanline
Applies a scanline visual effect - only draws every other line (TO REMOVE AT SOME POINT)
throttle_movement
For use in conjunction with realtime_interval - this stops you from moving crazy fast - repeated keypresses of the same movement direction will not increase your speed. This doesn't apply to the action button. If you can think of an example that requires action be throttled, just let me know and I'll try accommodate you.
verbose_logging
As you play the game, spits out information about all rules applied as you play, and also allows visual inspection of what exactly the rules do with the visual debugger. (make page for this)
zoomscreen [int width]x[int height]
Zooms the camera in to a WxH section of the map around the player, centered on the player.