DatapawWolf

Multiplayer is awesome. However doing MP requires an entire different way of thinking. And your having troubles adapting to the different thought process. This is going to make MP difficult. As a personal experience. I worked on a MP game with a co-worker. I did the entire networking side including writing the server in NodeJS and the client in C# Unity. All the other guy had to do is use 3 functions and understand network messaging. He understood the messages very quickly. But it's been 2 weeks and the networking thinking is still causing him troubles. Smart guy though. We have managed to get through enough.

Anyways stop thinking of Peer as being a player. Break that chain now. Peer != Player. Peed is any computer connected. So First Peer is the Host. Who says it's a player peer? Your assuming that a player is going to be a first peer and thus authoritative host. This is an incorrect form of thinking.

You can create a first room peer and run it on your dedicated hardware server. Thus your now controlling the authoritative information. This peer

A. Does not have a playable character or if it does it's out of bounds.

B. This peer NEVER logs out as it's run on your computer as the authoritive host.

I don't use Magicam much. I've only toyed with it. From what I saw no. But that's doesn't mean you can't. Can't be much more helpful on Mcam.

Instead of scaling the project. Scale the specific layers, So scale all but he UI layer.

While this game looks 2d. It in fact uses a lot of a lot 3D aspects. Such as mesh transformation.

You can do this in C2, but you would pretty much need to write you own plugin to handle the platforming beahviour that would mix with the Canvas plugin. You couldn't get a way with just using C2 core plugin behaviours. Doable yes, but only for expert developers.

What would be really nice is scene graph heiarchy for objects.

In Unity 1 object can only have 1 collision box. So it's not unusual for 1;1 ration. it's nothing new. However many engines I have worked with use SceneGraphs and non scenegraph engines like C2 are fewer out those I used.

A scene graph uses a parent->child relations. This makes the XY, Size, angle all relative values compared to the parent. While PIN does this to a lesser extent. it's a far inferior to scengraph.

In Unity when we need multi sensor objects. We create the core object and then child objects with additional colliders. Because unity uses Scenegraph this is easy. If I flip/rotate(ie Mirror) the object and children are mirrored with the parent. This makes handling multi part objects super smiple.

Now I love C2 more than Unity. Much more, but I do disagree with a few design decisions. PIN is not a replatement to Scenegraph design. And scenegraph design would fix a lot of problems developers have with C2 and object structuring.

Never had a problem with Dictionary. Can you post an image snippet of what your doing.

Also just to let you know. Current Key and Current Value only work right when your doing a specific Dictionary ForEach loop. There is a System ForEach, but Dictionary and Array both have custom loops. These loops use the refernece for Current XY stuff.

So if your doing CompareCurrent value with a CurrentKey and not in a foreach loop from Dictionary. It's going to fail.

"CurrentKey

CurrentValue

In a For each key event, these return the key and its value (respectively) for the current key being iterated."

https://www.scirra.com/manual/140/dictionary

My suggestion is to go to the Plugin maker for Clock which isn't Scirra. It's possible that the browser updated and some obscure code in the clock program is now using removed browser call.

You can also optionally go back a browser itterations and check those. Try a different browser. If it still persissts you can also go through the plugin and check out what's wrong with it.

lucid

Talking about the Sprite not the plugin. I'll make a small video to show what I'm doing and a written comment about what I thought it shuold do. That way you can let me know what I'm doing wrong

The benefit of Cordova is that you can write your own layer to core OS api's. That way the door is open to more oppertunities.

https://github.com/alongubkin/phonertc

While this api is not the solution we are looking for. it's a step in the right direction for someone to pursue WebRTC on IOS.

When it comes to fighting games and other smiilar attack frames. Most developers spawn the collision box on frame x, and destroy on frame y. Using image points in the frame and then setting angles seems to be a enough.

Though I agree it would be nice to have collision flags to determine how or what can collide with what or not collide with.

lucid

can we have the option to set new origin points for images. Mine seem to be locked now. Since some of the images have different points of visual center there seems to be no way to reposition them.

I noticed any fps below 45 causes the dt to produce less smootth results. I have no idea why that happens. dt is just a difference between last time and this time in a usable form. I have no problem in Unity's dt or using JS or Java custom dt. But C2's just goes herky jerky. I'm wondering if the dt is linked to the browser refresh hz.

I don't have excellent examples.