-
Notifications
You must be signed in to change notification settings - Fork 26
Not working with the new Elder Scrolls Legends client by Sparkypants released 2018-09-25 #236
Comments
same, waiting for update to upload my collection |
Hi @extesy do you need some help to deal with the new Legends' client ? Could you provide a roadmap or something ? I can try to help, the app is great and want to keep it alive. Cheers |
@extesy hasn't made a commit here in almost half a year. It's almost time to concede that this project is dead. |
24 guys fork this project. Could we create a little task force to try to restore it? I'm not skilled enough on C#/.Net to lead and it seems not so easy but I'm OK to help. |
@fabgrenier The C#/.NET part is the easy part. The problem is that, as far as I can tell, the Deck Tracker interfaces with the TESL client by directly reading from its undocumented memory space. It's quite a daunting task to do that and a big kudos to @extesy or whoever did it for the old client. I'm guessing that doing it for the new client would take a lot of time and effort. |
I read into the code quite extensively when I was trying to understand how it actually interfaces with the game. So I'd like to help or even take the initiative if I have time, to make something similar for the new client. I suppose @extesy is quite busy at times or not playing TESL much anymore. |
But I also heard that an in-game deck tracker is an upcoming feature for the new client. We could also just wait for that. |
I can't really code, but i love this and miss this and will totally send a ton of good karma to anyone who picks this up. |
R.I.P. :( |
Hey! |
doesnt wokt yet :( |
When I start version 1.0.78 of the Deck Tracker and then try to play the new Sparkypants client for Elder Scrolls Legends, it is never able to detect a running game. The "Running game" text says Elder Scrolls Legends, but it stays red, just like it did with the older Direwolf client when it wasn't detecting properly.
Any plans to support the new Sparkypants client?
The text was updated successfully, but these errors were encountered: