Update - 7th February

[jaxon]

Slowdown during online games has been fixed.
Crash when viewing inventories (pressing Tab) - fixed.
Auto-lose option added - if you're having a fight against creatures and you cannot possibly win, an Auto-Lose option appears to speed things up.
Game log has some text improvements, including better descriptions of object and follower usage and differentiating between battle and psychic combat.
Two summon spells could be cast during combat - fixed.
Enchant Blade works on magic weapons - REALLY THIS TIME.
When the Genie follower is on the board, an icon on the card shows how many spells it has.
Warhorse - the rule for losing the Warhorse is now correct, it will be discarded when you lose a life.
Crash when using the Hearth Rune after the Leper has shambled onto you - fixed.
Warlock Quest deck missing if you resume a game after playing a non-Reaper online game - fixed.
Merchant now starts with 4 fate points.

Known issue - whilst creatures roll their dice in combat, your spells temporarily flip around so you only see the back of the cards. This doesn't stop you casting spells, it's just a minor visual issue.

This update also includes all of the good things from yesterday's update, but none of the bad things.

[Felix Krowe]

Very cool - keep up the great work.

[rospondek]

jaxon58 の投稿を引用：

Crash when viewing inventories (pressing Tab) - fixed.

Tried to crash the game this way but I couldn't. My version was broken ;( It worked ;(
:D

Any news about last two broken achievements?
I mean:

Escape Artist - Escape from the Temple on the first try.
Unbeliever - Win a game without using fate.

[Peter B]

You guys are amazing, keep up the speed.

[jaxon]

The achievements are still being looked at, so any issues with them will still exist in this version.

[Little Nemo]

A suggestion.

About the Logs.

Am I really the only one that cries about it?

After moving a mouse cursor over the card's name, we should see a screen of that card. So a player will be aware what given card did during the game. Not everybody knows every single card in the game.

Again, please make the logs in the game more useful and usable.

[jaxon]

Nemomon の投稿を引用：

A suggestion.

About the Logs.

Am I really the only one that cries about it?

After moving a mouse cursor over the card's name, we should see a screen of that card. So a player will be aware what given card did during the game. Not everybody knows every single card in the game.

Again, please make the logs in the game more useful and usable.

It's a good idea, but it's a bit late in the development to add something like this, because each card name would have to be interactive, and bring up an image of the card big enough to read, so a bit like whenever you click a card in your inventory. We'll have a chat about it here, but I'm not sure if it'll make it into the game.

[nicki]

how to stop the game and read the card description, where is pause button to hold?

[jaxon]

Press the SHIFT key to pause the action in an offline game.

[nicki]

and also want to know, will be this month full release of a game and sales?

[jaxon]

jaceb の投稿を引用：

and also want to know, will be this month full release of a game and sales?

If all goes well, yes!

[?Syntax Error]

Very nice work again. great to see the regular updates and fixes.

One little bug keeps bothering me(and some other people too i guess).

It is the infamous "crash on exit", so whenever I quit the game from the main menu I will get a crash-report. It doesn't matter if I play offline or online, and I tried things like running in admin mode.

Probleemhandtekening:
Gebeurtenisnaam van probleem: APPCRASH
Naam van de toepassing: Talisman.exe
Versie van toepassing: 1.0.0.1
Tijdstempel van toepassing: 51f2aa63
Naam van foutmodule: Talisman.exe
Versie van foutmodule: 1.0.0.1
Tijdstempel van foutmodule: 51f2aa63
Uitzonderingscode: c0000005
Uitzonderingsmarge: 00047955
Versie van besturingssysteem: 6.1.7601.2.1.0.768.3
Landinstelling-id: 2067
Aanvullende informatie 1: 0a9e
Aanvullende informatie 2: 0a9e372d3b4ad19135b953a78882e789
Aanvullende informatie 3: 0a9e
Aanvullende informatie 4: 0a9e372d3b4ad19135b953a78882e789

Using Win 7 Home(64-bit), i7 core and 8GB ram.

I know that bug is not game breaking in anyway, but would it be possible to look into it? I don't like games crashing for no reason, and it would be nice to see it fixed. Only one of my other games has the same type of crash.

[rospondek]

I don't think that this aftergame crash should be fixed right now. Ok it can be a little annoying but if this crash doesn't break anything it can be fixed in the future. For now there are too many ingame bugs which should be fixed in the first place.

[00bins]

We haven't seen this crash on our dev builds / machines in the office. If we had we would be trying to fix it. Does it happen every time you run? Does it happen if you just go to the front-end and then quit?

[?Syntax Error]

bins の投稿を引用：

We haven't seen this crash on our dev builds / machines in the office. If we had we would be trying to fix it. Does it happen every time you run? Does it happen if you just go to the front-end and then quit?

It just happens everytime I run the game, doesn't even matter if I play the game. When I press quit on the main menu, the crash pop-up(the windows one, not the game itself) is there.

It is also always the same code, the crash-code that I posted in the log above. Could be anything I guess, drivers or memory-related. Maybe it doesn't matter but my videocard is Geforce GTX570 and the sound is onboard Realtek HD(also with latest drivers).

Other people have reported this crash as well here in the forums :

http://steamcommunity.com/app/247000/discussions/0/558746089828123444/

[<SNK>XAN7]

Great update! Good job! :)

Thx. ;>