Closed never147 closed 1 year ago
I had slightly improved the web-requests since the last week and then actually removed some of the web requests. But all that is moot because the source I was using has stopped posting NextTZ updates. Looking for another source currently. Have found one fella who apparently knows how to pull the data and apparently had it available via API for a moment but he says he's putting his spare time into D4 at the moment. In the next update (which I will be posting soon) I've added in a config option to disable NextTZ updates, I recommend setting this to false.
Sounds great thanks!
On Sun, 4 Jun 2023, 07:06 shupershuff, @.***> wrote:
I had slightly improved the web-requests since the last week and then actually removed some of the web requests. But all that is moot because the source I was using has stopped posting NextTZ updates. Looking for another source currently. Have found one fella but he says he's putting his spare time into D4 at the moment. In the next update (which I will be posting soon) I've added in a config option to disable NextTZ updates, I recommend setting this to false.
— Reply to this email directly, view it on GitHub https://github.com/shupershuff/Diablo2RLoader/issues/10#issuecomment-1575414281, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANGICEEWEMPWFJRA2EXXMDXJQQXPANCNFSM6AAAAAAYZXNPWA . You are receiving this because you authored the thread.Message ID: @.***>
Closing this as should be resolved in the new release. Give the new one a hoon and let me know if you see any similar issues.
I saw this new feature so thought I'd give it a go. It throws some errors for me.