# That was an interesting fight

**URL:** <https://community.gemsofwar.com/t/that-was-an-interesting-fight/852>\
**Category:** Gameplay Chat (PC/Mobile)\
**Created:** [October 6, 2015, 12:50pm UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852 "2015-10-06T12:50:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarvelKit](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/marvelkit/32/7072_2.png) [@MarvelKit](https://community.gemsofwar.com/u/MarvelKit)\
**Post date:** [October 6, 2015, 12:50pm UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852/1 "2015-10-06T12:50:38Z")

</div>

Only it wasn’t. GoW hung up on me, continuously playing some tsching sound. On the bright side: I didn’t loose the fight (so didn’t loose my bonus star in the next battle). On the other hand I lost my ‘investment’, some 500 gold or so to invade. 😄

 ![](https://us1.discourse-cdn.com/flex019/uploads/gemsofwar/original/1X/ff9442091e8e76a56614552b6b97f660b53e75a1.jpg)

Fun fact: I solved the confusion I had why the ‘chess board’ looks different from battle to battle. It shows clearly that it’s partly transparant and the background shows the invaded (or defended) kingdom. Never realised that before!

---

<div class="post-metadata">

**Author:** ![melkathi](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/melkathi/32/131_2.png) [@melkathi](https://community.gemsofwar.com/u/melkathi)\
**Post date:** [October 6, 2015, 4:49pm UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852/2 "2015-10-06T16:49:19Z")

</div>

So you invested 500 Gold into knowledge!

---

<div class="post-metadata">

**Author:** ![Gems-of-War](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/gems-of-war/32/2281_2.png) [@Gems-of-War](https://community.gemsofwar.com/u/Gems-of-War)\
**Post date:** [October 6, 2015, 11:48pm UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852/3 "2015-10-06T23:48:42Z")

</div>

> [@MarvelKit](#):
>
> it’s partly transparant and the background shows the invaded (or defended) kingdom.

Ya-huh! I love all the full screen Kingdom artwork 😃 I’ll pass this to @Full, but I have a feeling this has been resolved in the next update. Will pop back if this isn’t the case!

Edit: Confirmed, fixed next update

---

<div class="post-metadata">

**Author:** ![MarvelKit](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/marvelkit/32/7072_2.png) [@MarvelKit](https://community.gemsofwar.com/u/MarvelKit)\
**Post date:** [October 7, 2015, 8:00am UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852/4 "2015-10-07T08:00:43Z")

</div>

> [@CrowdedWorlds](#):
>
> Ya-huh! I love all the full screen Kingdom artwork 😃 I’ll pass this to @Full, but I have a feeling this has been resolved in the next update. Will pop back if this isn’t the case!
> 
> Edit: Confirmed, fixed next update

Strange, I wouldn’t have thought that was a bug but by design? I think it looks lovely, once you know what you’re looking at.

---

<div class="post-metadata">

**Author:** ![Gems-of-War](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/gems-of-war/32/2281_2.png) [@Gems-of-War](https://community.gemsofwar.com/u/Gems-of-War)\
**Post date:** [October 7, 2015, 11:38pm UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852/5 "2015-10-07T23:38:09Z")

</div>

> [@MarvelKit](#):
>
> Strange, I wouldn’t have thought that was a bug but by design? I think it looks lovely, once you know what you’re looking at.

Ah I meant the lock up, not the background 😛

---

<div class="post-metadata">

**Author:** ![MarvelKit](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/marvelkit/32/7072_2.png) [@MarvelKit](https://community.gemsofwar.com/u/MarvelKit)\
**Post date:** [October 8, 2015, 9:00am UTC](https://community.gemsofwar.com/t/that-was-an-interesting-fight/852/6 "2015-10-08T09:00:43Z")

</div>

Oh, I thought the lockup was just a glitch, not a bug. This was Windows 10 after all. 😛
