We built our website in C2, but it has some odd side-effects like undoing the MVC development model and makes pagination difficult.

CB Hash is a hash, not encryption. The only encryption that works on browsers is SSL, and that is seated in the browser, not the web application.

You cannot encrypt in JavaScript because the source is 100% available to any user of your website. So, people can just remove your encryption in the source.

Hashing is a one way process though, you cannot get the original data back out of it on the server.

You can hash it and have a comparison library on the server. I use something similar for the authentication on our website, but the server needs to have complete information or your comparison will fail.

As long as your secret is sufficiently complex, it will not be hackable.

Also, It is not entirely clear what you are trying to protect? Or are you just doing a non-repudiation scheme? The security will also depend very heavily on how you transmit your secret or the lifetime of the secret. Anyone with a wire shark and knowledge of which algorithm you are using can guess at your original information.

So please Scirra Team, make C3 as lightweight as possible but not so far that it will affect the feature list. Just make it cool and light.

I can't imagine them not making it lightweight, since that is one of the hallmarks of C2, but the weight and ease of use of C2 is why we selected C2 to begin with.

> The URL of your game is the address that you have it posted to.

>

> In order to do what you are asking, you have to have a server-side application talking to a database or cache.

>

That sounds complicated, kinda...

I've been doing some research and I've found a plugin called Cransberri, should I just buy that plugin and use it? Looks way easier.

Thanks for your response!

With the advent of virtual servers, it is really not bad now.

But that plugin might work for you too. It would talk to Google servers.

It seems we have more devs then testers here, lol. There are only three responses so far. :-p

> i wish the new C3 will have a really neat looking UI, like an adobe software

>

This. The UI in C2 works great, but doesn't look that great...

Who cares if it looks great. It is clean, understandable, simple, and easy to follow. That is all of their design goals.

Right, but the loop is not the problem. The inventoryArr is. You need to master control of that first.

If you pipe it out to a text object every tick, I guarantee you will have rogue entries in there. Then you just need to figure out where they come from. Usually, the timing will help with that, as you can see them appear in real time that way.

Did you put that condition on the click event?

Another way to debug is to disable events and see if that affects it. That is what I am doing right now to track down a JSON-AJAX bug.

Not without a server between them or a peer2peer connection (like the Multiplayer object).

Here's a request for C3 : auto-complete when calling functions() names.

That already exists...

You should make a debug Text object on your screen and output "InventoryArr.AsJSON" to it.

The inventory array is the sole determiner of the contents of your inventory.

If it is blank, then you can track when it is getting items added to it and see why.

When you open an empty inventory it should look like:

{"c2array":true,"size":[0,1,1],"data":[]}[/code:gtu1old7]
Otherwise, you will get rogue items appearing in your inventory.

That was why I added my debug text objects also, because I had some issues getting the example to work properly.  Do a search in your C2 for "InventoryArr" and find anywhere you are pushing objects to the array; those are where your problems will be.

Also, be aware that you can still click on your "Equip_chest" even if it is 0 opacity or invisible.  So you should probably put another condition on that event, like:
[code:gtu1old7]If Equip_chest is visible[/code:gtu1old7]OR[code:gtu1old7]If Equip_chest opacity > 10[/code:gtu1old7]

Make your sound files smaller?

Also, that should only happen the first time because most browsers will cache sound files.