revert 2008-02-06T01:44:30Z!alinkmaze@gmail.com (fixing sharing info with ally not using fog/shroud)
Having a consistent handling of this case have more implications than I thought Need more carefull analysis to decide if this little stupid case worth the WML check
This commit is contained in:
parent
a0f6180354
commit
9f9471b4a1
1 changed files with 1 additions and 1 deletions
|
@ -729,7 +729,7 @@ bool team::shroud_map::shared_value(const std::vector<const shroud_map*>& maps,
|
|||
return false;
|
||||
|
||||
for(std::vector<const shroud_map*>::const_iterator i = maps.begin(); i != maps.end(); ++i) {
|
||||
if((*i)->enabled_ == false || (*i)->value(x,y) == false)
|
||||
if((*i)->enabled_ == true && (*i)->value(x,y) == false)
|
||||
return false;
|
||||
}
|
||||
return true;
|
||||
|
|
Loading…
Add table
Reference in a new issue