Author Topic: [UPDATE] Playable Instruments  (Read 10838 times)

1.0.0 to 1.0.1
  • Removed className restrictions on playSong to make way for upcoming instrument events

Event_Instruments has been released!

PLEASE READ: I didn't realize until after I made these that Blockland removes semicolons from output events.  Rather than change the entire notation system, I simply made exclamation marks ! replace semicolons, but only for these events.

So basically, wherever you would normally use a semicolon, use an exclamation mark instead.  I know this inconsistency sucks, but I'd rather have this than screw up people's songs by changing how the notation system works.


Output Events (bricks only):
  • playNote
  • playRandomNote
  • playPhrase
  • playSong
  • setSongPhrase

Input Events:
  • onPhraseEnd
  • onPhraseLoop
  • onSongEnd
  • onSongLoop



Updated System_Instruments

1.0.2 to 1.0.3
  • Added processInputEvent callback onPhraseLoop for Event_Instruments update


1.0.1 to 1.0.2
  • Added getInstrumentFromIndex and isValidInstrumentIndex to InstrumentsNamespace class
  • Added processInputEvent callbacks onPhraseEnd, onSongEnd, and onSongLoop to make way for Event_Instruments add-on
« Last Edit: April 16, 2018, 01:20:50 AM by Electrk.. »



Are there files for the songs I've saved? If so where can I find them in my Blockland folder?

config/client/instruments/ and config/server/instruments/

config/client/instruments/ and config/server/instruments/
Thanks for the reply, I found a bug(?) and thought I would report it here, maybe its just my end though. Whenever I save a song to my server, sometimes it doesn't show up but is still considered "there". Whenever I try to save the file again it tells me the file already exists and doesn't show up in the songs list. Basically I can never actually load the song or save it again.

That shouldn't be happening, and it's never happened all the times I've used it.  Maybe it's a conflicting add-on?  Either way, if it's just something that happens sometimes and there are no reproducible steps to get the bug to happen, there's not much I can really do about it.
« Last Edit: April 16, 2018, 03:47:41 PM by Electrk.. »

if it's just something that happens sometimes and there are no reproducible steps to get the bug to happen, there's not much I can really do about it.
It happens every time I try to do it, here's an example. Also, it doesn't actually save, thank god I saved it to my local files or I would've lost 3 hours of work.




sounds like a write permissions issue

sounds like a write permissions issue
...so how would i fix it

Maybe it shouldn't say it was successful if it wasn't. Just so people don't end up losing stuff.
Just check if isFile or something.

...so how would i fix it

Check the security settings on the various file folders and make sure it allows writing

Maybe it shouldn't say it was successful if it wasn't. Just so people don't end up losing stuff.
Just check if isFile or something.

Just pushed an update

1.0.3 to 1.0.4
  • Error message now gets displayed when files fail to save properly

Check the security settings on the various file folders and make sure it allows writing
The files I save are there, It just looks like the GUI Isn't showing some of them in the server songs list. Any way I could fix that?

The files I save are there, It just looks like the GUI Isn't showing some of them in the server songs list. Any way I could fix that?
-snip-

I really don't know as I've never encountered this error before.  Maybe try navigating back to the root folder in the file browser (the two periods .. at the top) and then back to songs?