Jump to content

fiki574

Developer
  • Content Count

    791
  • Joined

  • Last visited

Everything posted by fiki574

  1. Hey. Thanks for the leaderboards report. The leaderboards on the Hub are being cached once every 36 hours, so maybe the data has not been cached yet. Also have in mind there are different time range selection possibilities, like so: At the start of every month, "This month" range usually doesn't have much data for the first week until players play the matches and fill it up. And could you please private message me with screenshots/examples of the time differences you're mentioning? It will help me better pinpoint the problem, if any.
  2. Hey. I've taken down the services on following URLs, as mentioned in the previous post: - auctions.skylords.eu - auctions.backend.skylords.eu - stats.skylords.eu - stats.backend.skylords.eu - leaderboards.skylords.eu - leaderboards.backend.skylords.eu The hostnames (DNS zone entries) will be brought done soon as well, until then they'll lead to an alphabetically first available URL on the system. Alongside this, I did some backend code refactoring (unnoticeable to end-users) and also added the support for "All Time" leaderboards time range, which was requested and ta
  3. Giving this as an upcoming heads up: I will be shutting down the "old" API frontend and backend applications on 30th of December (in 2 days from this post). Please make sure you've switched to the new Hub API. Affected and shut down services will be: - auctions.skylords.eu - auctions.backend.skylords.eu - stats.skylords.eu - stats.backend.skylords.eu - leaderboards.skylords.eu - leaderboards.backend.skylords.eu Thanks and regards.
  4. Please refer to this thread from now on:
  5. Hello everyone. This will be a very similar post and thread as the previous counterpart. I'll keep it short. Past few months, I've been working on a new, centralized UI and backend for the previously separated 3 API backends and frontends, from the upper linked thread. So, previous links are from now on obsolete/redundant, but will be still available for some time: GitHub repository: https://github.com/fiki574/Skylords-Reborn-API-UI Statistics: https://stats.skylords.eu/ Auctions: https://auctions.skylords.eu/ Leaderboards: https://leaderboards.
  6. Numerous times before it was said that just because there is not an official staff reply in a topic or suggestion, it does not necessarily mean we are not taking it into consideration or discussion behind the curtains. Demanding replies and/or personal attention does not speed up the process at all. Having in mind the lengths and extents this thread has went to, it is obvious it needs proper look at and preparation of a reply, because a lot of points have been touched. Also, why are we being compared to big game studios at all? Totally different history, totally different circumstances, t
  7. API breaking changes have been made to Auctions as well, so check them out and update accordingly: https://github.com/fiki574/Skylords-Reborn-API-UI/blob/master/Auctions/README.md#auctions-api
  8. Possibly, but requires additional mechanisms and logic. It will stay like this for now, however it might get improved at some point. Leaderboards are getting refreshed once every 6 hours, meaning that there are 4 refreshes which take, on average, 10-15 minutes to complete, which then results in the leaderboards being "unavailable" for barely an hour in a day.
  9. API breaking changes have been made to Leaderboards, check out the changes and update accordingly: https://github.com/fiki574/Skylords-Reborn-API-UI/blob/master/Leaderboards/README.md#leaderboards-api This week I plan on updating Auctions, so next Wednesday expect an API breaking changes/updates to the Auctions as well.
  10. Damn, I totally missed your post. 3 weeks late, but I've corrected the times now: https://github.com/fiki574/Skylords-Reborn-API-UI/tree/master/Auctions#auctions-api No such player-specific API for now. Ladders are with reason capped at 200 players: a) to match the ingame leaderboards and b) not to kill our database, because the current queries take almost 20 full minutes to execute and load data.
  11. Right, but I meant on someone who does not have access to our past versions of source code(s) and is doing it from scratch.
  12. What you described, is entirely possible and most likely done already to some extent, somewhere, from someone. What I was refering to (the complete emulation of our client so you get literal, proper programmatic bot), is almost impossible.
  13. Public API doesn't provide a way to interact with Auction House other than literally just displaying the live listings. Bids, buyouts, or botting is not possible with it. Proper, in-game bot that emulates our client and network architecture is hard, almost impossible to make (if you're not using one that scans the screen and use OCR to make mechanical clicks, i.e. literally move the mouse over the button and click it). TL;DR: There is no such thing as trade/AH bots here, and if there were, they would not be "legal".
  14. They server-sided replay generator is done since long time ago. Every match replay gets stored on the server, each of the replay is about few KBs big so it won't take too much space.
  15. No, misses the point of our API and is too resource heavy to have it on our side. That's why you can query our API and create your own history
  16. Hey. Define "long-term data" exactly.
  17. I did not see a single comment/post/thread similar to yours that states that the game is remotely unplayable, let alone completely. Even other players tell and prove otherwise, so the only straight out lie here is the one claiming that the state is completely unplayable. I will not even address other stuff as you fail to realize differences between hardware and software impacts/problems. Hardware as a whole is pretty beasty, however the software is not so much, which you you would expect from a server that was reverse engineered using client binaries, but then again I don't expect th
  18. Practically the same as you previous suggestion: Just differently worded.
  19. We don't have an infinite amount of achievements ideas. New ones are supposedly planned to be added, I don't know when.
  20. If you Google for "Skylords Reborn" and set the time filter to "Last week" or "Last month", you'll be able to see that quite some number of gaming mags and websites picked up the news already. However, there might be another form of "advertising" (or rather attracting interests into the game) planned, more on which would know either Zyna or Lada.
  21. Do you know difference between an open source and closed source repositories? Open source: opened source code to everyone to publicly use and contribute Closed source: closed source code from everyone to only creator and handpicked contributors So, in our case: Open source: frontend applications, and API specifications that can be found in respective README.md files in the respective GitHub repositories. Closed source: backend applications, actual API implementation of which the source is not publicly available, and will not be ever. No one is trying to make or port
  22. It is not recommended and in most cases not supported to have a request body in a GET request. Since you are sending a JSON to that endpoint, it should use POST. This is basics of web development and semantics. Frontend applications and API specifications are open-sourced, backend is not. I highly doubt you found many other errors cause I have no problems running any of the applications, be it frontend or backend, locally or on a VPS. You might have found some misstypes or inconsistencies, but I hardly doubt you found errors per se. All reports and suggestions are welcome here: https
  23. Never, unfortunately. Explained somewhere that it opens up too much boting possibilities. Yea, have a list but without images. https://auctions.backend.skylords.eu/api/cards/all
  24. Glad you like it. All suggestions are welcome here: https://github.com/fiki574/Skylords-Reborn-API-UI/issues Just the live listings.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use