# Ghosted Val Raven not giving Sigils

**URL:** https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387
**Category:** Bug Reports
**Created:** [September 24, 2018, 2:17pm UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387 "2018-09-24T14:17:36Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Strat](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@Strat](https://community.gemsofwar.com/u/Strat)
#### Post date: [September 24, 2018, 2:17pm UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/1 "2018-09-24T14:17:36Z")

</div>

I Killed Val Raven in the Raid event. It “ghosted”, so was dead but still displayed. I did NOT get my 2 additional Sigils at the end of the battle after winning.

Please check the [known issues list](https://community.gemsofwar.com/t/update-4-0-known-issues/45141) before posting a bug.

Note: If you are uncomfortable reporting your bug publicly you can privately message @Cyrup or @Kafka with the completed bug template.

**Platform, device version and operating system:**

**Screenshot or image:**

**What you were expecting to happen, and what actually happened:**  
_This is simply what you were trying to do and what happened instead. Example:_  
_‘I was trying to start an Arena battle, but Gems of War loaded Broken Spire quest instead!’_

**How often does this happen? When did it begin happening?**  
_Was this a once-off bug or has it been a consistent issue? Does it only happen after doing a particular game mode?_

**Steps to make it happen again**  
_Sometimes there are certain steps that can lead to a problem that may not be obvious!_  
_Example: I lose once in the Arena._  
_I then exit to the world map._  
_I then tap on Broken Spire on the map and then tap Arena._  
_Broken Spire’s quest loads instead of the Arena_

---

<div class="post-metadata">

### Author: ![Razzagor](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/razzagor/32/50037_2.png) [@Razzagor](https://community.gemsofwar.com/u/Razzagor)
#### Post date: [September 24, 2018, 5:35pm UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/2 "2018-09-24T17:35:42Z")

</div>

I had the same thing at a Delve event. I did reported in the Know issues thread, i hope they give some extra attention to this for a fix.

---

<div class="post-metadata">

### Author: ![Strat](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@Strat](https://community.gemsofwar.com/u/Strat)
#### Post date: [September 24, 2018, 9:41pm UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/3 "2018-09-24T21:41:02Z")

</div>

Dead ghosted troops have been a know bug for years. Unfortunately now with the way Val Ravens are coded this bug limits the player ability to progress 2 additional battles as a “Reward”.

I hope they fix this………

---

<div class="post-metadata">

### Author: ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)
#### Post date: [September 25, 2018, 1:49am UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/4 "2018-09-25T01:49:54Z")

</div>

Hi @Strat

The team put in a small fix for one variant of this issue awhile back, but it seems the issue has a different cause at this stage.

Can you please provide some more details:

1. Do you remember who was on your **Team** and who was on the enemy team?
2. Do you know what may have killed the enemy originally?
3. Were there any Doomskulls on the board when the Raven was supposed to be killed?
4. Please describe your internet: e.g. Ethernet, WiFi
5. What platform are you playing on?
6. Do you have any screenshots/videos?

---

<div class="post-metadata">

### Author: ![Strat](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@Strat](https://community.gemsofwar.com/u/Strat)
#### Post date: [September 25, 2018, 2:13am UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/5 "2018-09-25T02:13:31Z")

</div>

1. Yes but is so awesome, I don’t want to post it publicly;)
2. 2 I think.
3. No.
4. Hard Wired (of course), and great.
5. Xbox One X. Running production version (I’m not in the preview program)
6. Yes. I’ll PM both of them. Val Raven dead but un-selectable, and the post reward screen.

---

<div class="post-metadata">

### Author: ![Memleak](https://avatars.discourse-cdn.com/v4/letter/m/c68b51/32.png) [@Memleak](https://community.gemsofwar.com/u/Memleak)
#### Post date: [September 25, 2018, 7:28am UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/6 "2018-09-25T07:28:10Z")

</div>

Same thing happened to me in the delve event. Raven was on first position and was ghosted with 2 hp left. The raven was killed thanks to some skulls after an explode spells. It may had been doomskulls.

The second team was also killed by skulls. Third and forth units were killed by Yao Guai. At the end I didn’t got my 2 sigils. For delves this is insanely horrible since the ravens are so rare and those 2 extra sigils really mean a lot.

For your questions, it may help:

1. My team: Jar of Eyes (this caused the explosion and skulls that killed the raven) / Azura / Yao Guai / Queen Mab;
2. Skulls that dropped after explosion;
3. Yes, I had some doomskulls but I am not sure if there was a doomskull involved in the killing damage;
4. Mobile internet 4G, no connectivity issues, full signal;
5. Android (Huawei P10 Mate Pro)
6. No, when I realized what happened it was too late. I can provide details for you to find the specific game in case you do save them internally.

---

<div class="post-metadata">

### Author: ![Cyrup](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/cyrup/32/50181_2.png) [@Cyrup](https://community.gemsofwar.com/u/Cyrup)
#### Post date: [September 27, 2018, 5:31am UTC](https://community.gemsofwar.com/t/ghosted-val-raven-not-giving-sigils/46387/7 "2018-09-27T05:31:31Z")

</div>

Thank you, I have made a note of these points for the QA report.

The team put in a fix for this that goes into the next update, **but** it has not been tested or verified as working yet (this is more just to let you know that we’re looking into it)
