Pinned OGame API

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • I didn't mean to discard the XML version of the API. I think the API is awesome as it is right now.
      You are right about the browser freezing on older computers (and mobile devices)

      There are some problems with the spanish translation of the forum.
      File uploading breaks the page.


      BTW I realize there's not a big difference comparing the original xml file with my json version. I think the attached file could be compressed more (and it can be modified to be more readable).

      About the comparison with xpath, I'd save a modified version of the data in local Storage, with indexes (properties). Really fast:

      players: {player_100233: {name: John Doe, alliance_id: 23544}, player_100234: {name: John Lennon, alliance_id: 23543} }


      Bug (as seen in the edit message page):

      Fatal error: PHP notice in file
      /home/www/boards/board.origin.ogame.de/wcf/templates/compiled/22_0_14_attachmentsEdit.php
      (22): Undefined index: messageID
      Files

      The post was edited 4 times, last by NeoArc ().

    • Black Cat wrote:

      I agree with Francolino, it's not a good habit to use JSON for a big amount of data, because you must parse all data before reading them and you never need everything
      it takes too much time for nothing... when you can use XML to read the particular element you need at a moment, and read another element for instance 10 seconds later if you need it at this time (it's what i do here with players.xml and highscore.xml)

      which is correct for your usecase black cat. but there might be other applications where it is vice versa.

      there are many arguments that favor JSON over XML. in the end you will always find projects which are better suitable for one of em BUT you can't say that one is bad and useless.

      btw you talk from a browser which is parsing an ajax request right? the answer is a bytestream which than needs to be parsed whether it is json or xml. modern browsers surely will have been optimized for both so i would assume that your argument is neither a pro nor a contra for xml over JSON.

    • Black Cat wrote:

      JSON is a format for light-weight data exchange
      it could be use for serverData.xml but it doesn't make sense to use it for universe.xml for instance


      Why do you want to force JSON in one category? JSON is able to do 100% the same stuff like XML does.

      Even for big universe.xml would make sense as JSON. Please accept that somebody might want to use it as his personal favor or because his source code is better at reading JSON than XML. Or do you say "no I don't publish a book in bulgarian because not many do speak it"? This is just silly.
      Or otherwise said I would rather use a JSON parser of 200 loc in C# than importing a whole XML libary which lets my code increase by a huge amount.

    • Your argument is invalid. XML is not more flexible than JSON since both data description languages can do exactly the same.

      Nevertheless you are completly right that (AND ONLY if there can only be one) XML is most likely best way (for this problem).

    • Hello,

      This is caused by the DDos protection. Vega.de is under DDos attack since some days, i am not sure about Vega.es, but seems to be the same. You can't do anything as long as this attacks are ongoing.

    • Hello,

      I m thinking make a tool for exploit ogame API and i have some questions :

      1) There is a list of all ogame community ? Like en,de,fr ...

      2) About universes.xml, why not make a xml who regroup all server from all community ?
      Like :

      fr
      server1 ...
      server2 ...
      en
      server1 ...
      server2 ...

      .....



      3) What is the champs "bonusFields" in serverData.xml ?


      I gonna have lot question again later :D


      Thanx for help.