Robertvokac (talk | contribs) No edit summary |
Robertvokac (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
== Byte code == | == Byte code == | ||
| Line 6: | Line 4: | ||
planet blupi's bytecode has functions for creating, removing, and detecting blocks. if it was actually included with level data, it would be possible to make logic gates, leading to some crazy stuff. | planet blupi's bytecode has functions for creating, removing, and detecting blocks. if it was actually included with level data, it would be possible to make logic gates, leading to some crazy stuff. | ||
== Additional button == | == Additional button == | ||
Revision as of 20:44, 20 July 2024
Byte code
planet blupi includes a serializable scripting language to control all the entities. this makes it very easy to add new entity behaviors to the source code. and since the script is represented as bytes, scripts could be included with levels (if the developers ever implemented it)
planet blupi's bytecode has functions for creating, removing, and detecting blocks. if it was actually included with level data, it would be possible to make logic gates, leading to some crazy stuff.
Additional button
Jesse Savoie — 03/18/2023 1:23 AM Oh, and one more thing: I've given up trying to add a functional dream button to the SB2 editor. In the EXE file, 34970 - 349a0 controls what that button does, but it can't go past 349a7 without messing up another button, so I've hit a dead end.