1. We have added the ability to collapse/expand forum categories and widgets on forum home.
    Dismiss Notice
  2. All Civ avatars are brought back and available for selection in the Avatar Gallery! There are 945 avatars total.
    Dismiss Notice
  3. To make the site more secure, we have installed SSL certificates and enabled HTTPS for both the main site and forums.
    Dismiss Notice
  4. Civ6 is released! Order now! (Amazon US | Amazon UK | Amazon CA | Amazon DE | Amazon FR)
    Dismiss Notice
  5. Dismiss Notice
  6. Forum account upgrades are available for ad-free browsing.
    Dismiss Notice

(NAB) Swiss Mercenary has incorrect upgrade path

Discussion in 'Civ3 Conquests - Bug Reports' started by Pawel, Dec 7, 2003.

Thread Status:
Not open for further replies.
  1. Pawel

    Pawel Daimyo

    Joined:
    Mar 18, 2003
    Messages:
    625
    The Swiss Mercenary is part of the following upgrade path

    Spearman (bronze working) ->
    Numidian Mercenary (bronze working) ->
    Pikeman (feudalism) ->
    Musketman (gunpowder) ->
    Swiss Mercenary (feudalism) ->
    Musketeer (gunpowder) -> ...

    In order to have a consistent path the Swiss Mercenary should be moved before the Musketman or even the Pikeman.

    This bug can be verified by inspection in the editor.

    I have the UK version of the game with the 1.02 patch installed.
     
  2. warpstorm

    warpstorm Yumbo? Yumbo!

    Joined:
    Dec 19, 2001
    Messages:
    7,688
    Location:
    Snack Food Capital of the World
    This is not a bug at all and was very much intentional There is no way that you want the Swiss Merc 'upgrading' to the musketman. It is just about the best bargain in defensive units in the game. Forcing the Dutch to give that unit up for a musketman that costs twice as much and only has one extra attack point (not that useful for a defender) would have been a much worse design error.

    I argued very much for the current upgrade path. Sorry, if you don't like it, but there are good reasons why it is that way.
     
Thread Status:
Not open for further replies.

Share This Page