-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a plan to move to v2.2.3 ? Is this instance still maintained ? #5
Comments
Hello @L0wkey96 , sorry for the late reply, i was out of office 🌴 . Regarding your question: i think you are talking about Pathfinder version v2.2.4 ? https://github.com/goryn-clade/pathfinder/releases/tag/v2.2.4 . Because the instance Why is the public instance not on v2.2.4 you maybe asking? Because v2.2.4 did indeed fix the eve-scout api, but Thera routing is still broken goryn-clade/pathfinder#221 . There is a pull request pending goryn-clade/pathfinder#226 , but it has not been merged yet. Looking forward to you reply :) |
Hello @fleischsalatinspace thanks for the answer :) I hope you spent some good holidays, I indeed meant the v2.2.4. I used the instance of friends running the v2.2.4 and the Thera connection module was working so I assumed this version solved the issue. I'll ask my friends what they did to get Thera back up and working in their PF and get back to you if you're interested. |
Answer given to me was just: update to the last version. They just updated to latest version and Thera module has been working so far. |
This instance is going to shut down on 2024-10-31. Please use https://public.eve-pathfinder.online/ as stated here https://forums.eveonline.com/t/service-lost-in-w-space-public-private-pathfinder-hosting-discontinued-as-of-2024-10-31/334504/60 |
Pretty much the title :)
Is there a plan to move to v2.2.3 ? Is this instance still maintained ?
Been using this instance for small corp without infra, it's working well so far but having back the Thera connection would be nice (the issue with the new EVE scout API have been solved in v2.2.3).
The text was updated successfully, but these errors were encountered: