I created this new topic for sharing my progress with a game concept I am working on. The idea is to have multiple challenges to be completed to beat the game. Considering a base can only have 10 Sphere Creators max, there will likely be 10 challenges total. These challenges can all be done in any order and will eventually all be hooked up to a counter to show progress and allowing to fully reset the game.
I have shared some of the logic involved and how this logic evolved to be able to count the completed challenges in some replies linked below:
I saw a video with this base where a ball drops down upon a button press. The ball then ends up behind one of the windows at the bottom. I did not realise that the doors at the bottom were hooked up to the ByteBeat system, but I guess it explains the more or less randomness of the doors and therefor position it ends up in.
Just after the ByteBeat update released and I had been messing with it, I noticed that logic can be easily hooked up. I immediately realised this may have potential as there is a large range of signal speed possible. Not quite sure how much of this potential can be translated to the logic though. Some of the logic requires a full tick pulse to work, while some logic is still stuck with the 1 tick delay.
Roland Oberheim on Twitter had used the ByteBeat as well for the below creation.
I will certainly explore this some more to see what is possible.
Found out I have a big issue with the floor switches. Somehow their signal state is not properly reset upon a reload. For example: I finish a challenge with the ball on the floor switch, which means the output is triggered (ON state). I then save the game and reload the save. The ball will not be there anymore and it doesnât really matter where it is anyway, but it is NOT on the floor switch. The floor switch itself does not show âgreenâ, which makes perfect sense, because there is nothing on it. However, the signal output is triggered âblueâ (ON state), even though it shouldnât.
It will only fix itself when re-triggered. Problem is that I made it so the player can NOT reach this floor switch to prevent issues. Pushing the button to get the sphere reset to starting position, makes no difference. The floor switch output just remains in a triggered state. This completely messes up my plans, unless I figure out a way to reset its state properly ⌠sigh!
No way to âbypassâ the issue, unless manually re-triggering. Even the Proximity Switch has the same issue, so can not be used as an alternative either.
My brother has worked in IT support for many years. He tells of a fault diagnosis often shared between his colleagues.
Amongst communications engineers, the term âRTâ is a well-known acronym for âRadio Teletypeâ. Also well known is the acronym âFMâ, which indicates âFrequency Modulationâ.
My brotherâs investigations of userâs problems often result in the discovery of âRTFM Failureâ, which is what he writes on the job sheet. Unfortunately, in this case, âRTFMâ does not mean âRadio Teletype Frequency Modulationâ.
It is the user who has failed to RTFM - i.e. âRead The F***ing Manualâ.
@Polyphemus - I love that âRTFMâ was a folder name on an MIT server years ago.
Some claim that it came from an Army term ⌠âRead the field manual,â but I prefer the more direct interpretation. It sort of goes with âThe cause of he problem rests between the keyboard and chair.â And yes, I was a IT Helpdesk tech/manager for years.
