Spooky Scary Programming Contest 2018
Root / Site Discussion / [.]
Good thing the contest ended before I got the idea thenWould a TikTok port had been a good submission for this contest?If you made that, I’m sure all the sane people (and me) would have left SBS.
OK, voting is over! Thank you all for your participation! I'll get the badges out... ummmm soonish? It might have to wait until this weekend.
Anyway, winners! Nathaniel's Pumpkin Swing comes in first with 11 votes, with Prokuku's The Maze in second with 9 votes. A VERY close third goes to 12me21's Spooky Tetris (but you don't get a prize for being in third, sorry).
I'll get to the winners today about their prizes, but the badges might have to wait a while. I hope everyone enjoyed the contest!
I really hope they build on the language with SB 4.
I hope there will be stuff like:
- Polygon display capable of shading and texturing polygons (think a new namespace, like the SP, BG, and BGM namespaces, so POLYADD x1, y1, z1, x2, y2, z2, x3, y3, z3, color)
- Easier-to-use arrays, and maybe something like dictionaries or JavaScript objects, or Lua arrays.
- More dedicated data structures that still have those weird hacks (like a bool type that still shows up as 0 or 1, and still can be added to integers or real numbers)
- 3D sprite rotation, so SPROT id, roll, [pitch], [yaw] (pitch goes first because backwards compatibility, or at least only on COMPAT mode if it exists)
- Which leads to... DEPTH MODES. The default is draw order only, but you can change it to mean that the Z-value has an actual effect on the thing it renders. Default one means old programs will look the same.
- Editable editor. I'd love it if other programmers could write the editor so it shows variables in the autocomplete, and add help for user-defined functions.
JavaScript objects are being implemented into petit com 3.
http://smilebasicsource.com/page?pid=1228
JavaScript objects are being implemented into petit com 3. http://smilebasicsource.com/page?pid=1228I really like the speed and simplicity that vanilla SmileBASIC provides. This does look like a useful-as-heck library, but I mean something like this:
ACLS
EVENTS = [
{
X = 4,
Y = 10,
TEXT = "REALLY GREAT RPG 2 DELAYED TO 2023. 'Gotta focus on my grades' V360 said in a press release"
},
{
X = 4,
Y = 8,
TEXT = "Did you play the new Undertale demo? I'm so flipping hyped for it, but I'm also [redacted]"
},
{
X = 9,
Y = 10,
TEXT = "What's happening fellow gamers",
OPTION = {
TEXT = "Hello, world!"
}
}
]
?EVENT[0].X, EVENT[0].Y, EVENT[0].TEXT
That reminds me. I should've added Array Literals to the list.there is no nesting of objects, unfortunatelyAn easy workaround would be to store the nested object as a literal string. I'd take the performance drop if you could nest the objects. Another idea is to automatically convert this:
{
A: "Hello!",
B: {
Text: "Gaming",
X: 30
}
}To this:
{
A: "Hello!",
B.Text: "Gaming",
B.X: 30
}...If that's how it works. Maybe separate nested object things by using a dot character, and not allow dot characters in names of elements.You could also store reference names to other objects and reference them. Also, the object literal stuff has to fit on a single line and passed into a function.
DIM OBJECT[0],OBJECT2[0] OBJECT = OBJECT() OBJECT2 = OBJECT() ADD OBJECT2, "ME",100 ADD OBJECT, "REFERENCE","OBJECT2" VAR OBJECT2_ME = FEILD(VAR(FEILD(OBJECT,"REFERENCE")),"ME") PRINT OBJECT2_ME 'prints 100
