Okay I see the confusion. So socket.io comes in two parts. The server side and the client side. Server side, its just a simple library that you control on your server. I'm going to use node.js as the example for the backend frame work... you can use whatever backend frame work you're comfortable with like PHP or Django (python) etc. So you have your server, with socket.io, it will handle all the routing and stuff for you once you initialize it in your server code. You handle broadcasting and receiving messages from here. The client side that you're seeing on the website is just regular javascript code you see on most websites that simply creates a connection to your server. All that they're doing there is providing you with a CDN which is just a link to their javascript so you don't have to waste your own hosting resources to serve it to the end user. They also give you another link so you can just serve it yourself instead of using their convenient one. Again, this is just for the front end... with hyperPad, you don't need to worry about this side at all. All the client side code is presented as behaviours. With the client side you handle receiving messages from the server, and emitting messages to the server. It just provides a realtime link between the end user and your server. Edit: Finally, when they are saying Socket.io servers... they're talking about your socket.io server. They're just saying, "Your socket.io server provides this handy convenience if you don't want to deal with our CDN"

@Thecheater887 it might take a little longer that i thought, because i'm having an issue with world coordinates. But murtaza is helping with it.

I guess that makes sense, it's just hard to decide whether to buy a month or save up for lifetime, especially if I end up no longer using hyperPad.

You could try the share option to share assets on Hyperpad. (You need to have the project open for it to load)

@Hamed ok! Also, do you have an eta for a set collision behavior? I think Murtaza said that it was something you were planning on adding in the future!

@Aidan-Oxley It is a bit slower, but by this point you already have them waiting, so it's not really that big of an issue ;),

As a temporary work around to search... you can always google a hub project that you're looking for. eg google: hyperpad hub meteor and meteor will be the first result...

Oh yeah, I meant tags... editing post... done

Thanks! I'm sure whatever solution it is will be a start :D

Well, if you want it in the App Store, then yes apple restricts it. iOS apps are like sandboxed. No other app is allowed to talk to another (other than a few APIs that apple provides, like sharing). Inside of hyperPad we could allow it, but it would open up other issues and not consistent to how things should be done for the App Store. Ie. It works in hyperPad, but not in the App Store. You don't always have to be connected with http requests. It can sync up each time it goes online In Game 1: Looked at rock. Tell server TheCheater looked at rock in Game 1. Game 2: Check the server for any new database entries. Game logic Sees Thecheater looked at the rock. Awards you the rock. In the example above you just need internet once in a while to sync up. It won't be realtime with out internet though. But that doesn't really matter too much.

Thanks! And glad to hear it! I'm sure you've other more important things to do, but it will be a nice addition at some point :D

@Thecheater887 Yeah but you're not supercell, and neither are any other of our users. If our users max out the limitations and these becomes needed we'll look into it. For now, let's just see if users can create a a simple app that uses http requests at all. My feeling is we're quite a way off before it's needed. Hopefully I'm proven wrong.

@XGames MCPE is a game with strict rules. hyperPad is an app that allows you to make mobile games with unlimited programming. If the crash isn't a memory issue, (mostly these), it's often a logic issue. Logic issues mean users made the app crash with bad behaviour usage. There's nothing we can do here with logic issue crashes, that's on you. And memory/performance is only one issue. As I said we're a small team and need to focus. We're already spread thin as it is, and adding on another HUGE task for something that won't be as good as a dedicate app is not worth our time, or even the communities time. There are so many other things we can do instead of this. Also, it may seem like a small task for a simple sprite editor. But it's still lots of work. There's the planning phase to see how it will integrate with the existing hyperPad code, theres setting up the architecture and code, theres designing a UI to make it usable and since it's a complete new app it's a whole new UI, there is the actual programming part to make it all work. Then there is testing, testing to make sure it works, testing to make sure it's usable. After testing it requires more changes, either because of bugs or user feedback on usability. Then more coding and testing.. Then after 5 months or more, we can release something. It's hard work. If it was so easy, there would be more apps like hyperPad.. Or even you would make your own drawing app. Also, remember we're a business and we have bills to pay and it costs a lot of money to run hyperPad. We have to make decisions that are best for the business. Sometimes this means we can't add certain features to hyperPad.

@Murtaza i get that bit what of someone really does want their project to be branched but not posted

I was manly joking but that's neat, I guess.

@Murtaza I was going off of the fact that it seems like your behaviors are run, then the screen updated, then repeat. Not sure how that would work otherwise, but that's a different story for a different day,

@iTap-Development I'm not sure XD.

@Murtaza okay, that makes sense. That's good because I've noticed I don't get great performance on my iPad 4 but it works fine on my friend's iPad Air. I guess iPad 4 is becoming outdated already...

I agree about making it more clear on the editor side. I think the confusion lies with the fact that the end index is not clearly labeled. We'll play with the UI a bit to make it easier to understand.