MantisBT - VCMI
View Issue Details
0000275VCMIMechanics - Town structurespublic2009-12-02 00:232011-05-29 13:57
Zamolxis 
Ivan 
normalminoralways
closedfixed 
0.75 
0.8 
0000275: Mana Vortex acts differently than in H3 (though neither H3 acted according to its description)
Object description: "temporary doubles spell points for ANY garrison or visiting hero"

H3 actual behavior: "temporary doubles spell points once a week, to the first hero who enters in contact with it in that week (visiting or garrison, visiting having priority if both are in town when built or if we enter town screen for the first time in a new week)"

VCMI behavior: "temporary doubles spell points to ANY hero visiting it (can be all in the same day), but only once per game"

I guess we first need to decide whether we go for the H3 behavior or not. If yes, then we probably will need to update the description somehow.
No tags attached.
related to 0000735resolved Ivan H3 issue: Mana Vortex didn't act according to its description in H3 > How should VCMI handle it? 
Issue History
2009-12-02 00:23ZamolxisNew Issue
2009-12-02 09:33WarmongerStatusnew => assigned
2009-12-02 09:33WarmongerAssigned To => Warmonger
2010-01-01 11:23WarmongerNote Added: 0000539
2010-01-01 12:15WarmongerNote Added: 0000541
2010-01-01 12:15WarmongerStatusassigned => resolved
2010-01-01 12:15WarmongerFixed in Version => 0.89
2010-01-01 12:15WarmongerResolutionopen => fixed
2010-07-13 12:46ZamolxisNote Added: 0001087
2010-07-13 12:46ZamolxisStatusresolved => feedback
2010-07-13 12:46ZamolxisResolutionfixed => reopened
2010-07-13 14:09WarmongerNote Added: 0001101
2010-07-13 14:17ZamolxisNote Added: 0001103
2010-07-13 14:17ZamolxisStatusfeedback => assigned
2010-07-14 08:53ZamolxisNote Edited: 0001103bug_revision_view_page.php?bugnote_id=1103#r965
2010-07-14 08:54ZamolxisStatusassigned => feedback
2010-07-14 08:54ZamolxisDescription Updatedbug_revision_view_page.php?rev_id=967#r967
2010-07-14 08:55ZamolxisNote Edited: 0001103bug_revision_view_page.php?bugnote_id=1103#r968
2011-01-15 17:34IvanNote Added: 0001487
2011-01-15 17:34IvanStatusfeedback => resolved
2011-01-15 17:34IvanResolutionreopened => fixed
2011-01-15 17:34IvanAssigned ToWarmonger => Ivan
2011-05-29 13:47ZamolxisNote Added: 0001752
2011-05-29 13:47ZamolxisStatusresolved => closed
2011-05-29 13:57ZamolxisIssue cloned: 0000735
2011-05-29 13:58ZamolxisRelationship addedrelated to 0000735

Notes
(0000539)
Warmonger   
2010-01-01 11:23   
I fixed it so now it gives a bonus to first visiting hero this week who doesn't already have too much mana.
(0000541)
Warmonger   
2010-01-01 12:15   
Fixed in r1413
(0001087)
Zamolxis   
2010-07-13 12:46   
A small adjustment still needs to be made:

If Mana Vortex doubles a hero's spell points from, let's say, 30 (his max) to 60, and next week he comes back still with 60 spell points, but his Knowledge increased with +1 in the meantime (skill or artifact), the Mana Vortex should still impact this hero if it can now give him 80 (even though his max is normally just 40, still below the current 60 SP).
(0001101)
Warmonger   
2010-07-13 14:09   
What happens when the hero has less that 60SP but has gained knowledge in the meantime?
(0001103)
Zamolxis   
2010-07-13 14:17   
(edited on: 2010-07-14 08:55)
Are you asking about overnight behavior or next visit at Mana Vortex? I don't understand the scenario you're referring to, but for now I will assume you're asking about the following case:
- Hero has knowledge 3, but gets 60 SP from vortex
- Then casts a spell (e.g.: View Air) and is left with 56 SP
- Then gains +1 knowledge > SP should remain 56
- Then visits Mana Vortex same day > nothing should happen
- Then visits Mana Vortex next week > he should get 80 SP
(that is assuming he didn't gain more knowledge, nor did he used other spells in the meantime, in which case he remains at 56 SP - he cannot recover 1 SP / day because he's above the maximum 40, but also cannot lose w/o casting)

(0001487)
Ivan   
2011-01-15 17:34   
Fixed in rev 1918
(0001752)
Zamolxis   
2011-05-29 13:47   
Tested in 0.84 and confirmed as fixed now.