Ladadoos
-
Content count
3067 -
Joined
-
Last visited
-
@Vernichtungsofen Or anyone else receiving this bug, please send me your log.txt file found in Your Documents>Battleforge>Diag either via discord, forum PM or just here.
-
@Acidimpact Next time you get this error, could you send me your log.txt (either in PM or discord -> Ladadoos) in Your Documents/Battleforge/diag ?
-
Entering 'full' Lobby while not all slots are occupied
Ladadoos replied to Nerevar's topic in Report A Bug
@Nerevar "Why shouldn't he be able to?" Exactly for this reason: so that the leader isn't blocked out of his own match. And yes, the "open slots" number is as far as I know exactly what it says, open slots. If you are in a group with 4 people and only 2 are in slots, then there are still 2 open slots. -
It's no use to keep posting a screenshot of the error anymore. Thanks though, but 1-2 screenshots are enough
-
Entering 'full' Lobby while not all slots are occupied
Ladadoos replied to Nerevar's topic in Report A Bug
@MephistoRoss @Nerevar I believe the issue is that somehow the leader was able to go out of a slot. If I am correct this should never be possible. Maybe it was caused by: -
I would like to add that according to @GreenDelay (Tom), relogging multiple times didn't fix his issue. Also other random things like doing /invite Tom tries to invite tom instead of Tom it seems. Highly likely it's some name conflicts going on, but just mentioning this in case it isn't.
-
@BeSeN Should be fixed on next client update. Not sure when that will be, but you'll probably hear it from Discord.
-
Once it happens again, cold you send me your log.txt via Discord (Ladadoos) found in Your Documents>Battleforge>Diag ? Thanks Because the error is mentioning about not being able to write to that .txt file (log file).
-
@BeastSquirtle With logged in do you mean logged in or after you started to launch the game ?
-
@Lywingho This issue should be fixed. If anyone encounters it, please tell us and post your Your Documents>BattleForge>Diag>log.txt here!
-
Number 6
-
...
-
3 - Login Button disabled after using wrong password
Ladadoos replied to johnnybeta's topic in Resolved
@johnnybeta Like @TGDTom mentioned, there is a 1 minute cooldown after every login attempt. It's even written in the red error message, yeh. This is to semi-prevent people from spamming login. -
NAME: Buyout and bid buttons aren't disabled for own auctions SEVERITY: 3 LOCATION: Marketplace REPRODUCIBILITY: Always DESCRIPTION: Buyout and bid buttons aren't disabled for own auctions. Clicking these buttons doesn't do anything though. IsMyAuction(auction) seems to never return true.
-
I believe you should have received the reward for the quest regardless. It's a known bug that it shows you have the quest ( at 0 / 15 ) even though you completed it already. Nice to see you were able to play that much by the way
