In Need of Javascript/JSON expert

[Morgisto]

Its not about any advantage.Or hiding anything from anybody because most player are from US anyway.

We already do have and can decompile the SWF very very well. Its this last week that the server call issue has thrown a spanner in the works. Enabling GOD MODE and that is not an issue atm.As explained in a pm to Hamster. This game entails building fleets of ship which has become an issue of between 15 to 20 days to build a ship.We could shorten the build period.Now with the server call being put in place it has basically renededred the game useless because who want to play any game and wait 15 days to build a ship and then you need 5 ships toboot. So a fleet will take 60 days unless you wanna fork out R1000 to build them.Then they get damaged and that takes 24 hour to repair. SO all we want is to find out how they applied the server call and how to disable it if possible.

2 cases of beers or more may be in the order of the day.

regards

 

[Thor]

Its not about any advantage.Or hiding anything from anybody because most player are from US anyway.

We already do have and can decompile the SWF very very well. Its this last week that the server call issue has thrown a spanner in the works. Enabling GOD MODE and that is not an issue atm.As explained in a pm to Hamster. This game entails building fleets of ship which has become an issue of between 15 to 20 days to build a ship.We could shorten the build period.Now with the server call being put in place it has basically renededred the game useless because who want to play any game and wait 15 days to build a ship and then you need 5 ships toboot. So a fleet will take 60 days unless you wanna fork out R1000 to build them.Then they get damaged and that takes 24 hour to repair. SO all we want is to find out how they applied the server call and how to disable it if possible.

2 cases of beers or more may be in the order of the day.

regards

What game is this?

Is it online?

 

[Hamster]

If they implemented the call server side I highly doubt you'll be able to bypass it unless you can fudge the parameters and make it think you are building a lesser ship maybe...or mess with the date?

 

[Morgisto]

Battle Pirates is a flash Game www.kixeye.com

 

[Morgisto]

We thought it was server sided but have a reliable source which says it not Serversided. Some have got it working but their lips are zipped

 

[Morgisto]

This is the comment received fro the person in UK that has a working version

If he knows what he is doing he should look into JSON and start from there , that's all what I'm saying.
thnx..ill relay
thats a gr8 hlp...i hope

Morgs

 

[rorz0r]

If I understand correctly, there's some flash game that involves building ships and the devs screwed up by implementing the build time on the client side, and some other guys have managed to decompile the swf and change the json data in some way the at their ships build quicker. You've got the swf decompiled but have no idea what's happening in the json so you need someone to take a look at it?

 

[Morgisto]

EXACTLY

We are not rich but obviously would like to pay for a fix to our problem

 

[zippy]

In a popularity contest who wins: JSON or XML?
Whilst XML has far more things (i.e. functionality, features, ...) going for it; in a popularity contest who wins; personally I haven't used much if any used XML in any apps I've built in the last 6 years; JSON has always seemed the more logical choice.

Today there are arguably better alternatives to JSON, hence I said JSON is so yesterday .

Our .net devs wrote a service for us to call using XML. A year and a bit later they told us they are changing it JSON and we need change our service calls. When we asked why they are changing it, as whatever is wrong with xml, the service was stable, the reponse was that the xml was unnessarily large, and JSON was easier to read. So I asked then why did they insist on xml tags names which are +20 characters in size and why did they insist on returning an xml response which was 3 quarters white spaces if they where concerned about sizes. And as far as readability was concerned, we don't actually read the xml. Reading the XML was once off exercise and it really wasn't that hard and is a stupid reason to waste time rewriting an interface and having go through the whole process. The response was that JSON is the "latest" technology........... At that point, I realised I'm wasting my time

 

[[)roi(]]

Our .net devs wrote a service for us to call using XML. A year and a bit later they told us they are changing it JSON and we need change our service calls. When we asked why they are changing it, as whatever is wrong with xml, the service was stable, the reponse was that the xml was unnessarily large, and JSON was easier to read. So I asked then why did they insist on xml tags names which are +20 characters in size and why did they insist on returning an xml response which was 3 quarters white spaces if they where concerned about sizes. And as far as readability was concerned, we don't actually read the xml. Reading the XML was once off exercise and it really wasn't that hard and is a stupid reason to waste time rewriting an interface and having go through the whole process. The response was that JSON is the "latest" technology........... At that point, I realised I'm wasting my time

Lol... Self flagellation, sounds like your .Net devs are either bored or their manager's a bit of a loon.

 

[zippy]

Lol... Self flagellation, sounds like your .Net devs are either bored or their manager's a bit of a loon.

A lot of it is about wanting to pad cv's with what is perceived as being the "latest and greatest tech".

 

[Hamster]

A lot of it is about wanting to pad cv's with what is perceived as being the "latest and greatest tech".

Having "JSON" on your CV hardly means anything.

You can understand if their reasoning is to standardise on JSON accross the board, but if XML is already the standard then I don't see the point of converting. That being said, it is not entirely a bad idea to do it "just because" but it would be nice of them to help you guys convert and adapt on their time.

 

[[)roi(]]

Having "JSON" on your CV hardly means anything.

You can understand if their reasoning is to standardise on JSON accross the board, but if XML is already the standard then I don't see the point of converting. That being said, it is not entirely a bad idea to do it "just because" but it would be nice of them to help you guys convert and adapt on their time.

Agreed knowledge of standards means nothing (or stated differently the stuff you could learn in a day or 2).

As to the conversion: If the team has free time why not standardise; however with that being said, I immediately question: if the team has time to do standardisation (or more specifically fix what isn't broken), why do they need a permanent staff of developers; outsourcing seems an obvious conclusion.

 

[Hamster]

Agreed knowledge of means standards means nothing (or stated differently the stuff you could learn in a day or 2).

As to the conversion: If the team has free time why not standardise; however with that being said, I immediately question: if the team has time to do standardisation (or more specifically fix what isn't broken), why do they need a permanent staff of developers; outsourcing seems an obvious conclusion.

Sprint work done? "Do any dev you want" days (STD Bank gives us two days a month)?

 

[[)roi(]]

Sprint work done? "Do any dev you want" days (STD Bank gives us two days a month)?

Have been on either side: working for a corporate and working as a consultant. Never did I just want to jump in a develop something / change something?

Specifications are there for a reason + the last thing I'd want to do is to destabilise something just to adopt a new standard + if it was a public API it would be considered a good idea to support both XML and JSON.

 

[kolaval]

Soap is still very much in use for us. It is normally not a one sided decision, you use what both parties can use.

Any case your sloppy code and queries waste CPU cycles way more than processing soap/json.

 

[[)roi(]]

Soap is still very much in use for us. It is normally not a one sided decision, you use what both parties can use.

Any case your sloppy code and queries waste CPU cycles way more than processing soap/json.

Only if you assume everyone writes sloppy code, and we ignore data volume and transmission medium.

 

[kolaval]

I've seen enough to be thoroughly convinced.

 

[[)roi(]]

I've seen enough to be thoroughly convinced.

Lol... That has to be some really awful code to negate data size or transmission.

 

[kolaval]