Opened 8 years ago

Last modified 8 years ago

#3792 closed defect

[PATCH] Stackable auras — at Version 4

Reported by: fatherbushido Owned by:
Priority: Must Have Milestone: Alpha 21
Component: UI & Simulation Keywords: patch
Cc: Patch:

Description (last modified by fatherbushido)

This ticket is related to : #3522. Actually, auras are not stackable. But there is some side effects with capture. For example : If one have two macedonians theater (one and one captured), auras don't stack. But if one have one macedonian theater and one spartan theater (captured), auras stack.

Change History (9)

comment:1 by fatherbushido, 8 years ago

As discussed on irc with elexis and sanderd17, we can use other robust keys/identifiers for auras such that auras never stack. We also add an optional flag in auras template which always allow stacking.

comment:2 by fatherbushido, 8 years ago

Summary: Stackable auras[PATCH] Stackable auras

by fatherbushido, 8 years ago

Attachment: 3792.diff added

by fatherbushido, 8 years ago

Attachment: 3792.2.diff added

rebased on 17810

by fatherbushido, 8 years ago

Attachment: stackablewonder.diff added

This sets wonder as stackable.

comment:3 by fatherbushido, 8 years ago

According to our discussion :/irclogs, there is a problematic case. If player with civ A have for example a temple with an aura wich modify the same value by adding 5 and a player with civ B have a temple with an aura wich modify the same value by adding 10, what is expected ?

The patch have a good reaction and affects units with only one of this aura (the first which applies). But this situation may not occurs since it doesn't make sense. One solution that mimo's give is the following :

  • it would be nice to ensure that all auras have the same value for all civs
  • differences would be introduced by civ specific technologies (now that they can apply to auras) possibly autoresearched

So as tech will apply to the player civ, we don't care if it's temple A or B which applies its aura, since the value will be the same.

comment:4 by fatherbushido, 8 years ago

Description: modified (diff)

by fatherbushido, 8 years ago

Attachment: 3792.3.diff added

by fatherbushido, 8 years ago

Attachment: 3792.4.diff added
Note: See TracTickets for help on using tickets.