Im unsure what has broken, but I can scan planets all day and none of them are being picked up.
@Angellus is there something up? Anything I can help with?
1 Like
Does he play anymore? Are we forcing him to work on something when he’s moved on, lol? It does to end up resting on his shoulders and I know it can’t be mine cause i"m tech stupid!
1 Like
Yeah I was gonna say the same thing. I don’t think he’s playing anymore. And from his last posts he was disappointed with the way the game has been going. So tagging him might be a waste of time.
Sounds good. Boundless Info won’t be updated moving forward then. Just an FYI.
There are limited people with access to the Boundless API as I recall. I assume some other sites may have updated colors etc. looking at Boundless Crafting I can see my sovereign that I recently purchased, but it’s not showing the colors on Boundless Crafting and it’s definitely not showing up at all on Boundless Info.
I do have a hobby project that I started that handles some of what the other sites do by pulling from Boundlexx API, but unless I get an actual Boundless API key, not much I can do.
1 Like
Probably his bot shutdown or something, the api is working but the exo/world discovery aren’t refreshing so you wont be able to upload the colors since it doesn’t exist in the database.
1 Like
Hmm any way to recreate it
The api core is on github : boundlexx/boundlexx at master · AngellusMortis/boundlexx · GitHub
For the world discovery, is not that bad to recreate but the resources data is a bit more complex.
I know Symoid made a discord bot for the world discovery back then, not sure if he published it though. I know mutiple discord channels had it.
The method I was using for Steam authentication broke, so I can no longer use internal/undocumented game REST API endpoints. i.e. planet scanning. Anything that does not require the internal game API still works. Boundless Proxy UI still works, but only for worlds that are in Boundlexx API as there is no way for to fetch a new one. The “official” API also still works, and shop data should still be updating (but I know everyone just uses BUTT anyways).
Since Wonderstruck is no longer in charge and Monumental does not seem to care, I made the Boundless client code open source. Previously, the OSS library for Steam did not allow fetching Steam session tokens so I had to use a Node.js one to do. Python side, Node.js side. Ideally it should be pure Python now if it is possible.
But since the repo has not really been touched in so long, it needs a lot of work to get in a workable state. I accidently deleted the fork I made of djangorestframework-msgpack, so it needs extracted from the existing container and rehosted again on Github. Then the docker build needs to be working and ideally a Github Actions workflow is added to build new containers on a commit to master/default branch. If all of that happens and the auth problem is fixed, I can just pull in the new container in the k8s cluster and use it. I already manage like 50+ apps in my k8s cluster, so Boundlexx is not really any trouble to keep hosting. I just have not found the motiviation to actually fix the repo and update the code.
7 Likes
I appreciate all you’ve done to keep things going, esp. since there’s no personal motivation to do so. I thank you for that!
1 Like
Just a heads up: the packages don’t seem to be checked in (probably a good thing ^^) so you’d have to provide an alternative source for the existing container.