Obviously, it is possible to use ugBASIC to participate in the next “BASIC10Liner” competition, in the following categories:

CATEGORY	DESCRIPTION	OK?
PUR-80	A game in 10 lines of max 80 characters (w/abbrev.)
PUR-120	A game in 10 lines of max 120 characters (w/abbrev.)	✓
EXTREME-256	A game in 10 lines of max 256 characters (w/abbrev.)	✓
SCHAU	Any program in 10 lines of max 256 characters (w/abbrev.)	✓

You cannot join the PUR-80 category since ugBASIC is not a native BASIC like the PUR-80 category requires. In order to reduce space you can use one or two letters abbreviations for each instruction.

In order to produce an executable that meets the rules, you have to use the -1 option on command line version. As an alternative, if you are using UGBASIC-IDE, the option can be enabled by using the "10-Liner" Contest option on the Build menu.

No external data

Rule 1. Loading data or program parts from mass storage devices is not allowed. (→).

It is not possible to load images, text files or other data from external files. This is a very convenient feature of ugBASIC, because it allows you to decline a resource for various platforms. Unfortunately, the regulation does not allow this type of feature. To better ensure that this rule is met, the -1 option disables the load instructions (LOAD and the like) and the UGBASIC-IDE option does the same.

There are alternatives.

It is possible to substitute an inline definition for an external file, with the definition of a buffer that contains the equivalent binary data. In this case, however, it is necessary to reconstruct the native data. There is currently no function that converts a generic buffer (and it would take up too much space anyway).



Obviously, any static graphic resources can be replaced by drawings in real time, at startup, using drawing primitives.

drawer = LOAD IMAGE("drawer.png"): PUT IMAGE drawer AT 0, 0

can be replaced with

DRAW "BM0,0C8R14D1L14D1R14L12U1C5R10"

or, in a more compacted form:

Dr"BM0,0C8R14D1L14D1R14L12U1C5R10"

Compiled programs allowed

Rule: 3. Programs may be compiled (source must still be submitted) (→).

ugBASIC is a compiler, and compiled programs complies with this rule. You can still send your source separately, or list it using the LIST command.

Allowed POKEs

Rule: 5. POKEs are allowed. (→)

Although ugBASIC theoretically allows you to use POKE commands, you really shouldn't need them.

Listability

Rule: 10. The program must be listable (the LIST command must produce a readable program listing) (→).



Using the -1 option, a small runtime module will be inserted into the program, which will allow you to run the program (RUN command) or display it (LIST command).

Controls

Rule: 15. If the game is controlled with the keyboard, use "O" for left, "P" for right, "E" for up and "D" for down if possible; this takes into account the most important keyboard layouts (no disadvantages for emulator users with QWERTZ, QWERTY or AZERTY keyboards) (→).

You can use the KEY STATE command to respect this rule, if needed.