Search Results

Late reaction... I know, but I stopped playing because I don't like that the game is telling me when I should be playing it. Basically you need to be there when your fleetsave returns, you can never forget to fleetsave and you cannot do anything else that results in you not paying attention to the game. I know that I just pretty much described OGame, but it's still the reason for me to stop playing.

I'm not here to say that this is bad or good, the idea itself seems good, yet I didn't even know about tear-down res saving, so I have no opinion about that. What I am really interested in if it is JoKy (the lead dev?) that is making the decisions, or GF itself? In other words, are you being managed, or do you make these decisions on your own? I really think that you cannot use your personal opinion as an argument in any case as a dev, but if GF itself has decided that tear-down saving should go…

Thanks for the key, finally some testing can be done! I'm a little bit confused though, the key I received is only valid for the test server and does not seem to be ip-bound, should we be getting a key that is IP-bound and valid for all servers at a later moment?

For a new tool (similar to galaxy tool) I want to store the planets of a player, since both name and location are not permanent due to namechanges and relocation, I figured that I could use the planet-id that is present on lots of pages and in the XML APIs. Though I have a question: Does the unique planet-id remain the same when you successfully relocate a planet?

I understand that things can take longer as anticipated as I'm a developer myself too, but is it not a reasonable idea to set a maximum waiting time of say 1 or 2 weeks, so we know when we can expect them? No offense, but I think it's a bit weird that the OGame V6 API seems to be in the scope of your daily work (it appears in updates, etc.), but generating the API keys isn't and has to be done in your spare time, because without keys the API is not that useful for the users/developers

Quote from Valent: “I'm sorry for keeping you waiting but the api key generation is done only in spare time by the dev. It looks like he has no spare time lately with this avalanche of updates . I'll keep poking him :)” Generating an API key shouldn't take that long, a few minutes at most... Please please ask him to create the keys so we can continue our cool projects

Any new update on this?

Thanks already, this is goign to be of some help already! It seems however that this is some kind of PHP output of the JSON output, would it be possible to also give the raw JSON output?

Does anyone have an example JSON response for the spy reports part of the API? (Examples for the other types would also be welcome, but they have a lower priority) I cannot find detailed documentation for spy reports (only for combat reports) and I'm unable to test as it is taking way too long to obtain a key, really disapointed.

I have another question for requesting/using API keys. So my tool will be like GalaxyView, where users of the tool (for example players or alliances) will need to run their own server, let's call this server their instance. Now the issue is that every instance needs to have their own API key as they will most likely be hosted on different IP addresses, even though they are all the same application running the same code, the real issue is that the API application process seems to be aimed at prog…

I'd like to create a project for OGame that looks a bit like GalaxyTool or GalaxyView, not exactly sure how it was called. The idea is that users can submit espionage reports and that it will gather them on a local server (so not centralized with all players), then it will on the galaxy overview show which targets might be interesting and which ones are most definitely not interesting. Later on it might get more options that give the player the ability to make informed decisions (automatic fleet…