View Full Version : API for War Status ?
kamax
04-09-2017, 11:30 AM
Hello,
It would be nice to make the war status API public. I need it in android / iphone app i have build and want to refresh.
I already have some old info but it would be nice to have the latest and full info. I already have MP a guy from NGD but he no more reply.
Can someone give me this API that i can refresh my smartphone apps ?
Slartibartfast
04-09-2017, 01:24 PM
You should contact Adrian for all questions regarding API.
kamax
04-09-2017, 02:00 PM
Yes Adrian, i'll try again to contact him.
He give me some info in 2013.
Are you the owner of regnum sentinel website ?
Is boss respawn time in the API ?
Slartibartfast
04-09-2017, 02:07 PM
Yes, I created regnumsentinel. And no, there is no boss info in API.
kamax
04-09-2017, 02:16 PM
How do you get boss respawn time then ?
Slartibartfast
04-09-2017, 03:56 PM
How do you get boss respawn time then ?
Bosses respawn in 109 hours interval, so I do the math.
kamax
04-09-2017, 09:12 PM
Oh i see and you have to adjust every time the server reboot. It's a lot of work.
Slartibartfast
04-09-2017, 10:26 PM
Oh i see and you have to adjust every time the server reboot. It's a lot of work.
Not really, it's all fully automated. My site requires zero maintenance.
kamax
04-09-2017, 10:39 PM
Oh yes, you can check if the server is down since you probably have a script that run 24/24h. I had the smartphone wayin mind and i probably can't check if server is down all the time with a smartphone.
Slartibartfast
04-09-2017, 11:05 PM
Smartphone application is not enough for this. You need the server which will pull war status once a minute from NGD's server, store data and serve it to your mobile application. You can't access directly to NGD's servers from your application because of:
1. Access to NGD's server is limited from one IP only
2. There is API call limit, i think it's 60 calls per hour
Practically, you have a single API command - get_world_status which returns something like:
{
"haven": {
"capture_owners": {
"alsius_castle_capture_point": "alsius",
"alsius_door_capture_point": "alsius",
"alsius_fort_1_capture_point": "alsius",
"alsius_fort_2_capture_point": "alsius",
"ignis_castle_capture_point": "ignis",
"ignis_door_capture_point": "ignis",
"ignis_fort_1_capture_point": "ignis",
"ignis_fort_2_capture_point": "ignis",
"syrtis_castle_capture_point": "syrtis",
"syrtis_door_capture_point": "alsius",
"syrtis_fort_1_capture_point": "alsius",
"syrtis_fort_2_capture_point": "alsius"
},
"gem_owners": {
"gem_altar_alsius_1": "alsius",
"gem_altar_alsius_2": "alsius",
"gem_altar_ignis_1": "alsius",
"gem_altar_ignis_2": "ignis",
"gem_altar_syrtis_1": "syrtis",
"gem_altar_syrtis_2": "syrtis"
},
"relic_owners": {
"realm_relic_aggersborg": "realm_relic_altar_aggersborg",
"realm_relic_algaros": "realm_wall_power_source_syrtis_3",
"realm_relic_eferias": "realm_relic_altar_eferias",
"realm_relic_herbred": "realm_wall_power_source_syrtis_2",
"realm_relic_imperia": "realm_relic_altar_imperia",
"realm_relic_menirah": "realm_relic_altar_menirah",
"realm_relic_samal": "realm_relic_altar_samal",
"realm_relic_shaanarid": "realm_relic_altar_shaanarid",
"realm_relic_trelleborg": "realm_relic_altar_trelleborg"
}
}
}
And that's all the info you will get from API. All other higher level data should be derived from it.
Good luck :)
kamax
04-09-2017, 11:41 PM
Thanks for the info. For the moment, my old apps use a mix of 3 API call that are not IP limited. I was not aware of the one you give.
The old API i use is better for mobile use but as you have say, i need to build higher level information myself. Some of them need a server and i already have one but i don't think i'll use it for this.
NGD should provide information to external dev to build goodies around the game. It should not take a lot of time to add few lines like boss respawn time or at least last server reboot time.
And wihtout IP whitelist but somthing like 60 call per hour/IP like other popular API do to prevent some abuse.
If some NGD member read this, please give a answer of what you think about this.
Leily
04-17-2017, 04:58 PM
Hey
Slartibartfast is right, you have to contact Adrian for this kind of things.
Write an email with all your questions : adrian -at- ngdstudios.com :smile:
kamax
03-09-2018, 07:27 PM
How do you know about dragon wish, it's not in the answer ?
Slartibartfast
03-10-2018, 12:38 AM
How do you know about dragon wish, it's not in the answer ?
I do the math. I know when the invasion is started, and if gems are reset to their positions, abviously the wish is granted.
kamax
06-15-2018, 12:45 PM
Ok thanks, i have a half backed ios app now that use this new API.
I just need to understand boos respawn time.
It's every 109h but how to get a starting point ?
Is it 109h from respawn time or dead time ?
When the server reboot, whe have every 3 boss but does this affect the normal cycle or can we just continue the 109h cycle and the 3 "reboot boss" are extra ?
Slartibartfast
06-15-2018, 12:46 PM
Ok thanks, i have a half backed ios app now that use this new API.
I just need to understand boos respawn time.
It's every 109h but how to get a starting point ?
Is it 109h from respawn time or dead time ?
When the server reboot, whe have every 3 boss but does this affect the normal cycle or can we just continue the 109h cycle and the 3 "reboot boss" are extra ?
I'm not quite sure what's the reference time point of starting counting down 109 hours. I used few other fan sites to set this point in my app.
Redo_Ger
06-15-2018, 01:54 PM
Ok thanks, i have a half backed ios app now that use this new API.
I just need to understand boos respawn time.
It's every 109h but how to get a starting point ?
Is it 109h from respawn time or dead time ?
When the server reboot, whe have every 3 boss but does this affect the normal cycle or can we just continue the 109h cycle and the 3 "reboot boss" are extra ?
The bosses do respawn 109h after they have spawned the last time. Not after they were killed.
The serverdown respawns are extra.
kamax
06-24-2018, 11:04 PM
Thanks for your help !
vBulletin® v3.8.7, Copyright ©2000-2024, vBulletin Solutions, Inc.