Staff Diary: v1.0

Neil

Starting off, here’s the data our get player endpoint will return (status code 200):

Edit: alliance will not be a part of the response. To get alliance information use the /alliance endpoint

Neil

Back with another update on Day 2. We’ve setup /alliance in replacement of the alliance object in /player.

Here’s the 200 expected response:

Also, all of this information is being pulled from our Documentation (yes we’re finishing docs as we add new endpoints). You guys just won’t be able to access it for now.

Also, here are the possible response codes, if you have a day or two to spare, start coding with v0.2 with the information given. If you don’t want to mess around with response codes as of now (since they might change), there will ALWAYS be a “success” field in any of our responses which is a boolean so you can work with that.

All of this is subject to change (even if most of it won’t). Have fun!

Neil

/player response codes as I haven’t shared above:

Neil

almost completed, coming tomorrow along with /recruit 😉

Liam

That’s amazing that the development is going great. I’d recommend adding a /army endpoint which returns just your army and not the other stuff. (Useful if you only want to get your army).

I would also recommend being able to hire commanders or fire commanders through the API. What are the endpoints you’re planning to add from now?

Neil

Liam What are the endpoints you’re planning to add from now?

The endpoints I’ll be adding are the ones above (GET /player, GET /alliance, POST /alliance) and the following ones:

POST /recruit
GET /market/list
GET /army (Added from your suggestion)

I’m not sure if we’ll add the following endpoint but we’ll think about them:

POST /alliance/deposit
GET /commanders
POST /commanders/hire
POST /commanders/fire
GET /buildings
POST /buildings
GET /items
POST /items

All the schemas for these are created but they will probably change till the time I’m done making the endpoint so I’m not releasing them till the endpoint is done. I hope to get atleast /recruit and POST /alliance out tomorrow.

Liam

Neil Wow that’s alot of endpoints coming with v0.2, that’s going to be a great start.

I recommend adding a /forge endpoint used for ofcourse, forging. Also maybe a /inventory endpoint or you already have the /items one for that?

primedust

Neil Alliance isn’t necessary right now , because [REDACTED]
About commanders endpoints , they seem something “extra” to add to the bot. They are something you do once in a while to get a good commander but not something you do repetitively, so I don’t see how useful it can become.

While /items or /inventory is pretty solid endpoint , that I’m thinking to add an /inventory command too the next update that we do whatever.

Neil

Liam They aren’t coming with v0.2. That’ll be too much work to release in 1-2 days lol. They’ll be coming with upcoming versions.

I will probably add /alliance/deposit with 0.2 but I’m not sure. The confirmed ones above will be coming with 0.2. About the forge endpoint, I’ll think about it with @primedust. I’m trying to prevent botting so most of the “Main” endpoints won’t be accessible. I hope to add /npc and somehow a anti bot prevention mechanism for it.

I’ll let you all know tomorrow which ones are confirmed to be added in this version or later.

primedust

/recruit is great endpoint and it has quite great interest as of now.
/market_list seems useful to just navigate easier and /army probably a little excessive but it may come of use, in the end the more the better.

What WE (as discussed with Neil on Discord, lol) suggest is /event_attack to also come in api endpoints with a larger cooldown. The reason why WE would prioritize events over npcs is because events are something that you have to constantly be active as they change each month in contrast to npcs which are the same.

This way we may arise the interest for events and also the activity.

Neil

primedust All of those are already confirmed and will be added, I need your opinion on the unconfirmed ones below.

Neil

primedust first of all, pls don’t talk about updates here lol. Also yeah I already thought of adding /inventory which is basically like/commanders but for your items.

Neil

And for alliances I believe it’s a good qol feature for now, couldn’t hurt. I’ve also pretty much implemented it all so no point in not adding it now.

CozmoKitten

looks great so far! I agree /recruit will be very helpful, but I’d also like a /tower, /forge, and some way to see what tokens I have

Neil

CozmoKitten Wow, that was the hundredth post, nice. Anyways back to your question, there is no way to add towers without making it completely accessible to botters. We have no way to identify which guild they want to attack the tower in so we’d have to request a guild id, then we would have to perform some checks to make sure they’re in that guild, and then attack the tower.

You already see where this is going, people can attack towers every time they finish their cooldown using some simple code.

We could make another API setting like /notifications where you select a guild you want the towers and stuff to happen in, still would be the same case so I’m not going to be adding that.

We already plan to add /forge and /items (can be changed to /inventory)

CozmoKitten

Neil That’s fair. I like the /notifications idea, but it would also be helpful to know when my recruits are over? Maybe a /activeRecruits that returns a list of active recruits including the troop type and a unix timestamp of the completion time? would also like this as a feature (using discord timestamps) through a command. i don’t know if this is possible with however the bot is coded, but it would be useful

Neil

It’s day 3! We’ve added POST /alliance. Here’s the information about the endpoint:

200 OK expected response:

Responses:

Query Parameters:

Neil

Added POST /recruit here are the info ya’lls

200 OK expected response:

All responses:

Query Parameters:

Neil

We are on track to release v0.2 today with only 1 endpoint left. That is GET /market

Neil

Finished POST /market

200 OK expected response:

Responses:

Query Parameters: