@Hamed The Receiver Behaviour that had this problem, once it stopped working, no longer cared how I set the key. It simply stopped working. I had, quite literally, two keys with the same Event Key, and could turn one off and the other on, and see that only the new one worked, that the old one had bitten the bullet. Could never be reused, in any way. This is the first time I've seen this particular type of bug, where a behaviour node has seemingly lost contact with the hyperPad world. It took an enormous amount of time and testing to isolate it to this being the problem. It was about the last thing I thought could happen...

@iTap-Development No. It isn't possible to get them to stop and stay in sync with other objects. So it's not possible to restart them, and keep sync, either. These are all workarounds for the lack of sprite sheets, the lack of bitmap fonts and the lack of image swap transitions... oh, and the lack of referencing and addressable instances.

Hey, this thread Gave me the idea of making a project that would get the likes/dislikes of a game. I just published it...https://www.hyperpad.com/projects/yhxyx1t1

@Aidan-Oxley thanks. Strange, says I need to be a developer, but on the HyperPad website it says enthusiast tier gives you custom avatar? EDIT: Nevermind, enthusiastic tier says “Custom HUB Avatars” whilst developer tier says “Custom user profile”.

@Hamed Got it. Thank you! So the Get Array Value at Index Behaviour is creating a locally stored variable/pointer of whatever its lookup (get) from the array returns, for the use of local Box Containers, Value Behaviours and any other localised behaviours wanting to use it. I think. For anyone coming along in the future, this seems to be what's happening, in pseudo code (please correct me if I'm wrong, @Hamed), wherein * indicates a pointer. *myLookUplocalStorage = myArray[atIndex] myBoxContainer = *myLookUPlocalStorage myArray[atIndex] += 1 // myArray[atIndex] is now 1 bigger , but neither localStorage nor myBoxContainer know anything about this update myBoxContainer stores a pointer to the localised lookup (get), so whatever changes at that address is instantly reflected in myBoxContainer

Received your email and responded. Make sure you cancel through the iTunes/Apple subscription pages. https://support.apple.com/en-ca/HT202039 We don't have control over subscription billing, that's on Apples end.

@Thecheater887 It's alright, good sir. I found this does what I want: [image: 3640f220-af1b-4c19-9625-2c3a0ae40fa0.jpg]

@Deeeds Ok, have just 1 of the Play Sound behaviour (turned off) in any object in your scene that you know will never get destroyed or disabled. Whenever the player interacts with that element, use Behaviour On with the Play Sound behaviour selected.

@iTap-Development said in Understanding Duplicates of Mirrored Objects...: @Deeeds yes I know.... “conceptual” is the foundation of your vocabulary. As it is for everyone. On Chomskyan enlightenment, come for the political, historical, corporate and media insights, stay for the linguistics. It is, quite literally, more pertinent to programming languages, especially visual ones (and the articulation of programming paradigms, processes and concepts), than you can imagine.

@Aidan-Oxley resetting saved data in the pause menu didn’t work? That’s weird, I think that’s how I’ve got it fixed before.....

@Deeeds I guess since you keep changing it through the editor, it could make it a bit easier for you. But if there were no way to change the background through behaviours, it would make little sense to be able to get the background colour through behaviours.

@Action-Studio you have to ask the Hyperpad team to change it.

You can create a new scene for your start screen. If there are few behaviours and few objects it should load almost instantly. The first scene in the list of scenes will be the first to load.

@Aidan-Oxley that was it! I might try that again.

@Jack8680 spawn a particle object and use destroy object attached to play particles.

@Deeeds @Murtaza There is definitely something strange happening here. It only happens when you start to spawn more of these objects with the flash cycle behaviours. Have a look in this project: http://bit.ly/E04bqD Tap the green object to make the blue objects flash (5 times). After you see that work normally, maybe try it again, just in case. Then, tap on the blue objects to spawn duplicates of themselves to the right. Then tap the green box and watch the blue objects fail to cycle properly (specifically, the original ones act a little strange, but only for the first time, any other cycles after that work fine, and only after they spawn duplicates). Tap the green object again, the spawned blue objects will only flash once, while the originals do it all 5 times.