# Act III: Steel Campaign 700 Resource Cards Bug

**URL:** <https://forums.ageofempires.com/t/act-iii-steel-campaign-700-resource-cards-bug/289798>\
**Category:** III - Report a Bug\
**Created:** [September 20, 2026, 9:44pm UTC](https://forums.ageofempires.com/t/act-iii-steel-campaign-700-resource-cards-bug/289798 "2026-09-20T21:44:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![coyotekiller114](https://forums.ageofempires.com/user_avatar/forums.ageofempires.com/coyotekiller114/32/42278_2.png) [@coyotekiller114](https://forums.ageofempires.com/u/coyotekiller114)\
**Post date:** [September 20, 2026, 9:44pm UTC](https://forums.ageofempires.com/t/act-iii-steel-campaign-700-resource-cards-bug/289798/1 "2026-09-20T21:44:26Z")

</div>

### ▶ GAME INFORMATION

- **GAME BUILD #:** 100.19.18390.0
- **GAME PLATFORM:** Steam
- **OPERATING SYSTEM:** Windows 11

### ▶ ISSUE EXPERIENCED

The 700 res HC cards in Act III are classified as Age 3 cards in addition to the 1,000 res cards, instead of Age 2 where 700 res cards typically reside

### ▶ FREQUENCY OF ISSUE

- **100%** of the time / matches I play (ALWAYS)

### ▶ REPRODUCTION STEPS

Here’s the steps to reproduce the issue:

1. Play the Original campaign
2. Unlock the 700 res cards
3. Observe they are in Age 3 in the deck instead of Age 2

### ▶ EXPECTED RESULT

I don’t know if this is a bug or deliberate, but 700 re cards should typically be in Age 3.

### ▶ IMAGE

 ![20260919221409_1](https://forums.ageofempires.com/uploads/default/original/3X/5/f/5f05643bb69bfb0ae944a040177dfe9933d4821b.jpeg)

### ▶ GAME FILES (SAVE / RECORDING)

N/A Home city issue

---

<div class="post-metadata">

**Author:** ![vividlyplain](https://forums.ageofempires.com/user_avatar/forums.ageofempires.com/vividlyplain/32/177091_2.png) [@vividlyplain](https://forums.ageofempires.com/u/vividlyplain)\
**Post date:** [September 21, 2026, 11:28pm UTC](https://forums.ageofempires.com/t/act-iii-steel-campaign-700-resource-cards-bug/289798/2 "2026-09-21T23:28:14Z")

</div>

This one is easily caught during QA… oh wait
