You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user guide.md
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Bot execution modes
32
32
33
33
### Unexpected behavior with 🎬 mode animations
34
34
35
-
We use the beebjit `-fast` parameter to achive very fast emulation in the accelerated modes, the only downside being some unexpected 'relativistic' effects if your code relies on external timers. In this mode CPU time is accelerated several thousandfold and decoupled from timing of BBC Micro peripherals and timers which remain emulated in real-time. This means flashing colours in the palette, and `*FX 19` or `INKEY` based timing will not work well!
35
+
We use the beebjit `-fast` parameter to achieve very fast emulation in the accelerated modes, the only downside being some unexpected 'relativistic' effects if your code relies on external timers. In this mode CPU time is accelerated several thousandfold and decoupled from timing of BBC Micro peripherals and timers which remain emulated in real-time. This means flashing colours in the palette, and `*FX 19` or `INKEY` based timing will not work well!
36
36
37
37
If your code waits for an external timer based event like VSYNC the video will appear to freeze. It's recommended to use `FOR ... NEXT` loop based delays in code you intend to run with 🎬 mode for that reason. The emulator takes a screenshot every 40,000 emulated 6502 cycles (which is the same period as VSYNC) and so resulting animation will still look [pretty much the same on a real machine](https://twitter.com/bbcmicrobot/status/1356755101587697669?s=20).
38
38
@@ -49,7 +49,7 @@ The [Owlet Editor](https://bbcmic.ro) is designed specifically for creative codi
49
49
50
50
## Reducing code size
51
51
52
-
One of the fun and challenging aspects of the bot is you need to squeeze your code down in size - code golf! Techniques to do this have evolved over time, many pioneered by [Rheolism](https://botsin.space/@rheolism). Here we outline some fundamental approaches, this is by no means comprehensive.
52
+
One of the fun and challenging aspects of the bot is you need to squeeze your code down in size - code golf! Techniques to do this have evolved over time, many pioneered by [Rheolism](https://oldbytes.space/@rheolism). Here we outline some fundamental approaches, this is by no means comprehensive.
53
53
54
54
```
55
55
10 PRINT "HELLO WORLD"
@@ -89,12 +89,14 @@ Note that some byte values must be ORed with 0x100 in order to map to a valid Un
89
89
90
90
### base2048 encoding [deprecated for Mastodon due to larger post length]
91
91
92
-
[Base2048](https://github.com/qntm/base2048) is a Unicode encoding optimized for transmitting binary data through Twitter. Using base2048 gives you an extra 100 characters of BBC BASIC code in a tweet, bringing it to ~384 characters in total. However our Hello World tweet will no longer be human readable. For this reason we no longer support base2048 on the Mastodon bot.
92
+
[Base2048](https://github.com/qntm/base2048) is a Unicode encoding optimized for transmitting binary data through Twitter. Using base2048 allowed an extra 100 characters of BBC BASIC code in a tweet, bringing the total to ~384 characters. However our Hello World tweet would no longer be human readable:
93
93
94
94
```
95
95
༣Ȝǁঐ౭चؼ๗ԪʢࠁನȤ3
96
96
```
97
97
98
+
For this reason and because the Mastodon bot supports 512 characters we no longer support base2048.
99
+
98
100
## Advanced minification techniques
99
101
100
102
### VDU and graphics commands
@@ -123,4 +125,4 @@ PRINT D?A
123
125
NEXT
124
126
```
125
127
126
-
In this example the first value returned would be 116, the ASCII value for the letter `t`. You can create a Twitter-friendly byte string to use in a `REM` from comma separated data with the [VDU to string tool](https://8bitkick.github.io/vdu/)
128
+
In this example the first value returned would be 116, the ASCII value for the letter `t`. You can create a Mastodon-friendly byte string to use in a `REM` from comma separated data with the [VDU to string tool](https://8bitkick.github.io/vdu/)
0 commit comments