|
Apr
25 |
|
answered | What to do in long games with players who are way behind? |
|
Apr
22 |
|
comment |
Can regeneration save my creatures from Turn // Burn? @ikegami The point in showing 4th ed's rules was to prove that the intended flavor for regeneration is that something gets mortally wounded, but then regenerates so that it doesn't die. The regeneration shield is a mechanism for cleanly converting that flavor to a stack-based system. It is indeed clean, and it usually corresponds perfectly with the flavor of regeneration, but sometimes it doesn't. |
|
Apr
19 |
|
comment |
Can regeneration save my creatures from Turn // Burn? @ikegami See Nick's comment about how it was implemented in 4th Edition. Here are details: wizards.com/Magic/Magazine/Article.aspx?x=mtg/daily/feature/52b |
|
Apr
19 |
|
comment |
Can regeneration save my creatures from Turn // Burn? @ikegami Because a card doesn't say "Add a regeneration shield," it says "Regenerate." The rules translate that into adding a shield because that's the simplest way to make the mechanic work in a stack-based game, but it leads to some not-very-flavorful edge cases. Flavor-wise, regeneration is something that you do after you've been injured that causes you not to die, but it's too complicated to model it that way in Magic. |
|
Apr
18 |
|
comment |
Can regeneration save my creatures from Turn // Burn? The fact that you can give something extra regeneration shields "just in case" reflects some serious weirdness in the regeneration rules. |
|
Apr
17 |
|
awarded | Teacher |
|
Apr
16 |
|
accepted | Mousemove in Watir |
|
Apr
16 |
|
answered | Ruby OR || syntax with an object |
|
Apr
1 |
|
comment |
Why doesn't django automatically update the foreign key? (obj.relative.id != obj.relative_id) Maybe you meant to save order before assigning it to self.order? Thanks again for the help! |
|
Apr
1 |
|
revised |
Why doesn't django automatically update the foreign key? (obj.relative.id != obj.relative_id) clarified |
|
Apr
1 |
|
comment |
Why doesn't django automatically update the foreign key? (obj.relative.id != obj.relative_id) Hm, I'm not sure I see the difference between your code and mine. It's clear that doing self.order=Order() sets self.order_id to None, but self.order.save() doesn't set self.order_id --- it just sets self.order.id. That's kind of weird, right? The only difference between your block of code and mine is that yours creates a variable 'order' instead and then assigns it to self.order, whereas mine works directly on self.order. |
|
Mar
29 |
|
answered | Can somebody continue a road after it has been cut off/separated from its nearest city? |
|
Mar
27 |
|
revised |
Why doesn't django automatically update the foreign key? (obj.relative.id != obj.relative_id) tidying |
|
Mar
27 |
|
comment |
Why doesn't django automatically update the foreign key? (obj.relative.id != obj.relative_id) You're right, but that's actually what I have in my code already (it'd generate an infinite loop as-written) -- I've now updated the question. |
|
Mar
25 |
|
asked | Why doesn't django automatically update the foreign key? (obj.relative.id != obj.relative_id) |
|
Mar
2 |
|
awarded | Popular Question |
|
Mar
1 |
|
awarded | Popular Question |
|
Feb
11 |
|
awarded | Popular Question |
|
Feb
11 |
|
awarded | Popular Question |
|
Dec
8 |
|
awarded | Nice Question |
