Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Error update required.
Lostshotgan
#1 Posted : Saturday, June 9, 2018 6:07:47 AM(UTC)
Lostshotgan

Rank: Member

Groups: Registered
Posts: 29
Man

Thanks: 11 times
Was thanked: 1 time(s) in 1 post(s)
I am constantly trying to update to 10.6.5.8, but it always shows me that an update is needed.
Plus it doesn't work by constantly showing "default".
At the same time on version 10.6.4 everything works fine.
Downloading the latest version from the site, rebooting the game and the bot did not help.

What do I do?
Lostshotgan
#2 Posted : Sunday, June 10, 2018 6:52:25 AM(UTC)
Lostshotgan

Rank: Member

Groups: Registered
Posts: 29
Man

Thanks: 11 times
Was thanked: 1 time(s) in 1 post(s)
The problem remains. A new version of the bot has already been released, and it is impossible for me to update to it. The bot does not work, only version 10.6.4 allows me to use it.
Can I send you a log or something? Just everything worked well and that's the trouble for the second day ...
Twister
#3 Posted : Sunday, June 10, 2018 10:25:10 AM(UTC)
Rank: Member

Groups: Registered
Posts: 27

Thanks: 5 times
Was thanked: 3 time(s) in 3 post(s)
Might be a silly question, but i don't understand why you can't update if you were able to download the latest version from the website? I get that you have issues with the update using the launcher, but if you're able to download the latest version from the site you should be on the latest version anyways?
Lostshotgan
#4 Posted : Sunday, June 10, 2018 11:19:44 AM(UTC)
Lostshotgan

Rank: Member

Groups: Registered
Posts: 29
Man

Thanks: 11 times
Was thanked: 1 time(s) in 1 post(s)
Twister;56655 wrote:
Might be a silly question, but i don't understand why you can't update if you were able to download the latest version from the website? I get that you have issues with the update using the launcher, but if you're able to download the latest version from the site you should be on the latest version anyways?

Even downloading the latest version from the site says that the update is necessary. Do-again writes. If everything was so simple I would not write here)
Wednesday13
#5 Posted : Sunday, June 10, 2018 12:45:53 PM(UTC)
Rank: Member

Groups: Registered
Posts: 18

Thanks: 1 times
Lostshotgan;56657 wrote:
Even downloading the latest version from the site says that the update is necessary. Do-again writes. If everything was so simple I would not write here)


Dumb question, but... Are you deleting files or copying your previous "config" file into the new instalation? If so, then that's why. You should add instead of replacing.
Lostshotgan
#6 Posted : Monday, June 11, 2018 4:59:14 AM(UTC)
Lostshotgan

Rank: Member

Groups: Registered
Posts: 29
Man

Thanks: 11 times
Was thanked: 1 time(s) in 1 post(s)
Wednesday13;56658 wrote:
Dumb question, but... Are you deleting files or copying your previous "config" file into the new instalation? If so, then that's why. You should add instead of replacing.

I tried to flip configuration files, tried to run a completely new downloaded version ... The bot just does not work. I'll wait for the help of the admin, what else can I do ...
Twister
#7 Posted : Monday, June 11, 2018 6:21:59 AM(UTC)
Rank: Member

Groups: Registered
Posts: 27

Thanks: 5 times
Was thanked: 3 time(s) in 3 post(s)
Lostshotgan;56659 wrote:
The bot just does not work.
Well I'm not the admin, but if you're stuck at the launcher.exe to update the bot you should still be able to start the bot by running the hearthranger.exe instead.
Though I guess this is nothing new to you, because you wrote that you can run with 10.6.4 without issues? Anyways, you might need to add more detail to what you're procedure of starting the bot is and especially provide more information what your issue looks like or the bot state reports before anybody could help you. At least to me (as a guy who was working in IT support before) it's still not clear where you encounter your issue upon starting the bot application and what you meant in your first post with this sentence: "Plus it doesn't work by constantly showing default."


Lostshotgan
#8 Posted : Monday, June 11, 2018 5:40:16 PM(UTC)
Lostshotgan

Rank: Member

Groups: Registered
Posts: 29
Man

Thanks: 11 times
Was thanked: 1 time(s) in 1 post(s)
Twister;56660 wrote:
Well I'm not the admin, but if you're stuck at the launcher.exe to update the bot you should still be able to start the bot by running the hearthranger.exe instead.
Though I guess this is nothing new to you, because you wrote that you can run with 10.6.4 without issues? Anyways, you might need to add more detail to what you're procedure of starting the bot is and especially provide more information what your issue looks like or the bot state reports before anybody could help you. At least to me (as a guy who was working in IT support before) it's still not clear where you encounter your issue upon starting the bot application and what you meant in your first post with this sentence: "Plus it doesn't work by constantly showing default."



23:39:01:DEBUG::hr socket port - 14400
23:39:03:INFO::Checking game environment..
23:39:04:INFO::Login Binding Server...
23:39:04:INFO::Login success.
23:39:04:DEBUG:: client : ver.10.6.6.2
23:39:04:DEBUG:: language : ruRU
23:39:04:DEBUG::starting bot .. 1
23:39:04:DEBUG::starting bot .. 3
23:39:04:DEBUG::starting bot .. 4
23:39:04:DEBUG::starting bot .. 5
23:39:04:DEBUG::starting bot .. 6
23:39:04:DEBUG::starting bot .. 7
23:39:06:DEBUG::starting bot .. 8
23:39:06:DEBUG::starting bot .. 9
23:39:06:DEBUG::waiting core data transfer ...
23:39:06:INFO::loading data...50%
23:39:06:INFO::loading data...100%
23:39:07:DEBUG::waiting core data transfer ...
23:39:08:DEBUG::waiting core data transfer ...
23:39:09:DEBUG::waiting core data transfer ...
23:39:10:DEBUG::waiting core data transfer ...
23:39:11:DEBUG::waiting core data transfer ...
23:39:12:DEBUG::waiting core data transfer ...
23:39:13:DEBUG::waiting core data transfer ...
23:39:14:DEBUG::waiting core data transfer ...
23:39:15:DEBUG::waiting core data transfer ...
23:39:16:DEBUG::waiting core data transfer ...
23:39:17:DEBUG::waiting core data transfer ...
23:39:18:DEBUG::waiting core data transfer ...
23:39:19:DEBUG::waiting core data transfer ...
23:39:20:DEBUG::waiting core data transfer ...
23:39:21:DEBUG::waiting core data transfer ...
23:39:22:DEBUG::waiting core data transfer ...
23:39:23:DEBUG::waiting core data transfer ...
23:39:24:DEBUG::waiting core data transfer ...
23:39:25:DEBUG::waiting core data transfer ...
23:39:26:DEBUG::starting bot .. 10
23:39:26:DEBUG::starting bot .. 11
23:39:26:INFO::TransitStateMachineFromOffline
23:39:26:DEBUG::starting bot .. 12
23:39:26:INFO::initializing...
23:39:27:INFO::initializing...
23:39:27:INFO::TransitStateMachineFromOffline
23:39:27:INFO::initializing...
23:39:28:INFO::TransitStateMachineFromOffline
23:39:28:INFO::initializing...
23:39:28:INFO::TransitStateMachineFromOffline
23:39:28:INFO::initializing...
23:39:29:INFO::TransitStateMachineFromOffline
23:39:29:INFO::initializing...
23:39:29:INFO::TransitStateMachineFromOffline
23:39:29:INFO::initializing...
23:39:30:INFO::TransitStateMachineFromOffline
23:39:30:INFO::initializing...
23:39:30:INFO::TransitStateMachineFromOffline
23:39:31:INFO::initializing...
23:39:31:INFO::TransitStateMachineFromOffline
23:39:31:INFO::initializing...
23:39:31:INFO::TransitStateMachineFromOffline
23:39:32:INFO::initializing...
23:39:32:INFO::TransitStateMachineFromOffline
23:39:32:INFO::initializing...
23:39:32:INFO::TransitStateMachineFromOffline
23:39:33:INFO::initializing...
23:39:33:INFO::TransitStateMachineFromOffline
23:39:33:INFO::initializing...
23:39:33:INFO::TransitStateMachineFromOffline
23:39:34:INFO::initializing...
23:39:34:INFO::TransitStateMachineFromOffline
23:39:34:INFO::initializing...
23:39:34:DEBUG::load vision deck config from directory -
23:39:34:INFO::TransitStateMachineFromOffline
23:39:34:INFO::load vision deck config success - default
23:39:35:INFO::TransitStateMachineFromOffline
23:39:35:INFO::TransitStateMachineFromOffline
23:39:36:INFO::TransitStateMachineFromOffline
23:39:36:INFO::TransitStateMachineFromOffline
23:39:37:INFO::TransitStateMachineFromOffline
23:39:37:INFO::TransitStateMachineFromOffline
23:39:38:INFO::TransitStateMachineFromOffline
23:39:38:INFO::TransitStateMachineFromOffline
23:39:39:INFO::TransitStateMachineFromOffline
23:39:39:INFO::TransitStateMachineFromOffline
23:39:40:INFO::TransitStateMachineFromOffline
23:39:40:INFO::TransitStateMachineFromOffline
23:39:41:INFO::TransitStateMachineFromOffline
23:39:41:INFO::TransitStateMachineFromOffline
23:39:42:INFO::TransitStateMachineFromOffline
23:39:42:INFO::TransitStateMachineFromOffline
23:39:43:INFO::TransitStateMachineFromOffline
23:39:43:INFO::TransitStateMachineFromOffline
23:39:44:INFO::TransitStateMachineFromOffline
23:39:44:INFO::TransitStateMachineFromOffline
23:39:45:INFO::TransitStateMachineFromOffline
23:39:45:INFO::TransitStateMachineFromOffline
23:39:46:INFO::TransitStateMachineFromOffline
23:39:46:INFO::TransitStateMachineFromOffline
23:39:47:INFO::TransitStateMachineFromOffline
23:39:47:INFO::TransitStateMachineFromOffline
23:39:48:INFO::TransitStateMachineFromOffline
23:39:48:INFO::TransitStateMachineFromOffline
23:39:49:INFO::TransitStateMachineFromOffline
23:39:49:INFO::TransitStateMachineFromOffline
23:39:50:INFO::TransitStateMachineFromOffline
23:39:50:INFO::TransitStateMachineFromOffline
23:39:51:INFO::TransitStateMachineFromOffline
23:39:51:INFO::TransitStateMachineFromOffline
23:39:52:INFO::TransitStateMachineFromOffline
23:39:52:INFO::TransitStateMachineFromOffline
23:39:53:INFO::TransitStateMachineFromOffline
23:39:53:INFO::TransitStateMachineFromOffline
23:39:54:INFO::TransitStateMachineFromOffline
23:39:54:INFO::set bot pause.
23:39:54:INFO::TransitStateMachineFromOffline
23:39:54:INFO::Bot paused.
23:39:56:INFO::resume bot
23:39:57:INFO::Bot is running.
23:39:57:INFO::TransitStateMachineFromOffline
23:39:58:INFO::TransitStateMachineFromOffline
23:39:59:INFO::TransitStateMachineFromOffline
23:39:59:INFO::TransitStateMachineFromOffline
23:40:00:INFO::TransitStateMachineFromOffline
23:40:00:INFO::TransitStateMachineFromOffline
23:40:01:INFO::TransitStateMachineFromOffline
23:40:01:INFO::TransitStateMachineFromOffline
23:40:02:INFO::TransitStateMachineFromOffline
23:40:02:INFO::TransitStateMachineFromOffline
23:40:02:INFO::Bot stopped.
Lostshotgan
#9 Posted : Thursday, June 21, 2018 6:34:36 PM(UTC)
Lostshotgan

Rank: Member

Groups: Registered
Posts: 29
Man

Thanks: 11 times
Was thanked: 1 time(s) in 1 post(s)
I'm sorry, Admin, but the problem was as it was. How can I solve it? Send you log files? Or how?
ustica
#10 Posted : Friday, June 22, 2018 2:53:41 AM(UTC)

Rank: Advanced Member

Groups: Registered
Posts: 133
Location: Malta

Thanks: 13 times
Was thanked: 21 time(s) in 20 post(s)
same problem here
dominquepaul
#11 Posted : Tuesday, July 3, 2018 8:54:06 AM(UTC)
Rank: Newbie

Groups: Registered
Posts: 2

I am also having a similar problem. Can the dev or anyone else help with this?

Basically, the bot was working correctly until update 10.6.6.6, but now constantly says it needs to update itself to version 10.6.6.6 even though it has already installed the 10.6.6.6 update. This update notification problem appears to be in an infinite loop, and the bot no longer initiates contact with the game and only outputs "TransitStateMachineFromOffline".

As another poster already mentioned, I re-installed the latest stable version (10.6.6) and inserted my CustomConfig files individually into the CustomConfig directory, and manually inserted corresponding deck assignments into the default deck_config.ini file. Those are all the changes I made to the file system before encountering this problem.

Below is from the logfile when I most recently tried to use the bot:

7:45:06 PM:DEBUG::hr socket port - 14400
7:45:09 PM:INFO::loading data...50%
7:45:09 PM:INFO::loading data...100%
7:50:29 PM:INFO::Please start game.
7:51:16 PM:INFO::Checking game environment..
7:51:16 PM:INFO::Please wait, checking..11
7:51:17 PM:INFO::Please wait, checking..10
7:51:18 PM:INFO::Please wait, checking..9
7:51:19 PM:INFO::Please wait, checking..8
7:51:20 PM:INFO::Please wait, checking..7
7:51:21 PM:INFO::Please wait, checking..6
7:51:22 PM:INFO::Please wait, checking..5
7:51:23 PM:INFO::Please wait, checking..4
7:51:24 PM:INFO::Please wait, checking..3
7:51:25 PM:INFO::Please wait, checking..2
7:51:26 PM:INFO::Please wait, checking..1
7:51:27 PM:INFO::Please wait, checking..0
7:51:29 PM:INFO::Login Binding Server...
7:51:30 PM:INFO::Login success.
7:51:30 PM:DEBUG:: client : ver.10.6.6.6
7:51:30 PM:DEBUG:: language : enUS
7:51:30 PM:DEBUG::starting bot .. 1
7:51:30 PM:DEBUG::starting bot .. 3
7:51:30 PM:DEBUG::starting bot .. 4
7:51:30 PM:DEBUG::starting bot .. 5
7:51:30 PM:DEBUG::starting bot .. 6
7:51:30 PM:DEBUG::starting bot .. 7
7:51:32 PM:DEBUG::starting bot .. 8
7:51:32 PM:DEBUG::starting bot .. 9
7:51:32 PM:DEBUG::waiting core data transfer ...
7:51:33 PM:DEBUG::waiting core data transfer ...
7:51:34 PM:DEBUG::waiting core data transfer ...
7:51:35 PM:DEBUG::waiting core data transfer ...
7:51:36 PM:DEBUG::waiting core data transfer ...
7:51:37 PM:DEBUG::waiting core data transfer ...
7:51:38 PM:DEBUG::waiting core data transfer ...
7:51:39 PM:DEBUG::waiting core data transfer ...
7:51:40 PM:DEBUG::waiting core data transfer ...
7:51:41 PM:DEBUG::waiting core data transfer ...
7:51:42 PM:DEBUG::waiting core data transfer ...
7:51:43 PM:DEBUG::waiting core data transfer ...
7:51:44 PM:DEBUG::waiting core data transfer ...
7:51:45 PM:DEBUG::waiting core data transfer ...
7:51:46 PM:DEBUG::waiting core data transfer ...
7:51:47 PM:DEBUG::waiting core data transfer ...
7:51:48 PM:DEBUG::waiting core data transfer ...
7:51:49 PM:DEBUG::waiting core data transfer ...
7:51:50 PM:DEBUG::waiting core data transfer ...
7:51:51 PM:DEBUG::waiting core data transfer ...
7:51:52 PM:DEBUG::starting bot .. 10
7:51:52 PM:DEBUG::starting bot .. 11
7:51:52 PM:INFO::TransitStateMachineFromOffline
7:51:52 PM:DEBUG::starting bot .. 12
7:51:53 PM:INFO::initializing...
7:51:53 PM:INFO::initializing...
7:51:53 PM:INFO::TransitStateMachineFromOffline
7:51:54 PM:INFO::initializing...
7:51:54 PM:INFO::TransitStateMachineFromOffline
7:51:54 PM:INFO::initializing...
7:51:54 PM:INFO::TransitStateMachineFromOffline
7:51:55 PM:INFO::initializing...
7:51:55 PM:INFO::TransitStateMachineFromOffline
7:51:55 PM:INFO::initializing...
7:51:55 PM:INFO::TransitStateMachineFromOffline
7:51:56 PM:INFO::initializing...
7:51:56 PM:INFO::TransitStateMachineFromOffline
7:51:56 PM:INFO::initializing...
7:51:56 PM:INFO::TransitStateMachineFromOffline
7:51:57 PM:INFO::initializing...
7:51:57 PM:INFO::TransitStateMachineFromOffline
7:51:57 PM:INFO::initializing...
7:51:57 PM:INFO::TransitStateMachineFromOffline
7:51:58 PM:INFO::initializing...
7:51:58 PM:INFO::TransitStateMachineFromOffline
7:51:58 PM:INFO::initializing...
7:51:58 PM:INFO::TransitStateMachineFromOffline
7:51:59 PM:INFO::initializing...
7:51:59 PM:INFO::TransitStateMachineFromOffline
7:51:59 PM:INFO::initializing...
7:51:59 PM:INFO::TransitStateMachineFromOffline
7:52:00 PM:INFO::initializing...
7:52:00 PM:INFO::TransitStateMachineFromOffline
7:52:00 PM:INFO::initializing...
7:52:00 PM:DEBUG::load vision deck config from directory -
7:52:00 PM:INFO::TransitStateMachineFromOffline
7:52:00 PM:INFO::load vision deck config success - default
7:52:01 PM:INFO::TransitStateMachineFromOffline
7:52:01 PM:INFO::TransitStateMachineFromOffline
7:52:02 PM:INFO::TransitStateMachineFromOffline
7:52:02 PM:INFO::TransitStateMachineFromOffline
7:52:03 PM:INFO::TransitStateMachineFromOffline
7:52:03 PM:INFO::TransitStateMachineFromOffline
7:52:04 PM:INFO::TransitStateMachineFromOffline
7:52:04 PM:INFO::TransitStateMachineFromOffline
7:52:05 PM:INFO::TransitStateMachineFromOffline
7:52:05 PM:INFO::TransitStateMachineFromOffline
7:52:06 PM:INFO::TransitStateMachineFromOffline
7:52:06 PM:INFO::TransitStateMachineFromOffline
7:52:07 PM:INFO::TransitStateMachineFromOffline
7:52:07 PM:INFO::TransitStateMachineFromOffline
7:52:08 PM:INFO::TransitStateMachineFromOffline
7:52:08 PM:INFO::TransitStateMachineFromOffline
7:52:09 PM:INFO::TransitStateMachineFromOffline
7:52:09 PM:INFO::TransitStateMachineFromOffline
7:52:10 PM:INFO::TransitStateMachineFromOffline
7:52:10 PM:INFO::TransitStateMachineFromOffline
7:52:11 PM:INFO::TransitStateMachineFromOffline
7:52:11 PM:INFO::TransitStateMachineFromOffline
7:52:12 PM:INFO::TransitStateMachineFromOffline
7:52:12 PM:INFO::TransitStateMachineFromOffline
7:52:13 PM:INFO::TransitStateMachineFromOffline
7:52:13 PM:INFO::TransitStateMachineFromOffline
7:52:14 PM:INFO::TransitStateMachineFromOffline
7:52:14 PM:INFO::TransitStateMachineFromOffline
7:52:15 PM:INFO::TransitStateMachineFromOffline
7:52:15 PM:INFO::TransitStateMachineFromOffline
7:52:16 PM:INFO::TransitStateMachineFromOffline
7:52:16 PM:INFO::TransitStateMachineFromOffline
7:52:17 PM:INFO::TransitStateMachineFromOffline
7:52:17 PM:INFO::TransitStateMachineFromOffline
7:52:18 PM:INFO::TransitStateMachineFromOffline
7:52:18 PM:INFO::TransitStateMachineFromOffline
7:52:19 PM:INFO::TransitStateMachineFromOffline
7:52:19 PM:INFO::TransitStateMachineFromOffline
7:52:20 PM:INFO::TransitStateMachineFromOffline
7:52:20 PM:INFO::TransitStateMachineFromOffline
7:52:21 PM:INFO::TransitStateMachineFromOffline
7:52:21 PM:INFO::TransitStateMachineFromOffline
7:52:22 PM:INFO::TransitStateMachineFromOffline
7:52:22 PM:INFO::TransitStateMachineFromOffline
7:52:23 PM:INFO::TransitStateMachineFromOffline
7:52:24 PM:INFO::TransitStateMachineFromOffline
7:52:24 PM:INFO::TransitStateMachineFromOffline
7:52:25 PM:INFO::TransitStateMachineFromOffline
7:52:25 PM:INFO::TransitStateMachineFromOffline
7:52:26 PM:INFO::TransitStateMachineFromOffline
7:52:26 PM:INFO::TransitStateMachineFromOffline
7:52:27 PM:INFO::TransitStateMachineFromOffline
7:52:27 PM:INFO::TransitStateMachineFromOffline
7:52:28 PM:INFO::TransitStateMachineFromOffline
7:52:28 PM:INFO::TransitStateMachineFromOffline
7:52:29 PM:INFO::TransitStateMachineFromOffline
7:52:29 PM:INFO::TransitStateMachineFromOffline
7:52:30 PM:INFO::TransitStateMachineFromOffline
7:52:30 PM:INFO::TransitStateMachineFromOffline
dominquepaul
#12 Posted : Tuesday, July 3, 2018 11:20:36 PM(UTC)
Rank: Newbie

Groups: Registered
Posts: 2

UPDATE: Bot now works. See below for fix info.

Apparently since the 10.6.6.6 update, Windows Defender software (the default Windows 10 antivirus software shipped with the operating system) apparently has stealth-blocked Hearthranger's boot.dll file. Thus, to make Hearthranger work again, open Windows Defender and add the Hearthranger folder to the "Exceptions" list. Then, try updating the game again.
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.173 seconds.