Re: [Warzone-dev] [Warzone 2100 Trac] #636: Shared sensors among allies

[Warzone 2100 Trac]

#636: Shared sensors among allies
-+--
Reporter:  Per   |   Owner:  Per  
Type:  defect|  Status:  closed   
Priority:  major |   Milestone:  unspecified  
   Component:  Engine: other | Version:  svn/trunk
  Resolution:  fixed |Keywords:  sensors teams
Operating_system:  All/Non-Specific  |   Blockedby:   
Blocking:|  
-+--
Changes (by sendai):

  * status:  accepted => closed
  * resolution:  => fixed


Comment:

 (In [7765]) Add the ability of allied players to share each others'
 sensors. Since iterating over all structures
 by all players to see if we could use each as a sensor would be rather
 time consuming, I created a
 new set of lists (currently with only one member) that sorts objects by
 function. This way we can
 very quickly iterate over all sensors, even when there are several hundred
 buildings on the map.
 Closes ticket:636.

-- 
Ticket URL: 
Warzone 2100 Trac 
The Warzone 2100 Resurrection Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone 2100 Trac] #636: Shared sensors among allies

[Warzone 2100 Trac]

#636: Shared sensors among allies
---+
 Reporter:  Per|  Owner:  Per 
 Type:  defect | Status:  accepted
 Priority:  major  |  Milestone:  unspecified 
Component:  Engine: other  |Version:  svn/trunk   
 Keywords:  sensors teams  |   Operating_system:  All/Non-Specific
Blockedby: |   Blocking:  
---+

Comment(by Per):

 New version of the patch. It fixes a few bugs, and generalizes the code to
 be utilized also for droids. Currently this support for droids has little
 effect, however, due to a number of bugs in the action code that I do not
 want to fix in this patch.

 It works the other way, though. You can take a sensor droid for a walk,
 point at interesting enemy structures, and sit back to watch the archangel
 missile battery fireworks.

-- 
Ticket URL: 
Warzone 2100 Trac 
The Warzone 2100 Resurrection Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone 2100 Trac] #636: Shared sensors among allies

[Warzone 2100 Trac]

#636: Shared sensors among allies
---+
 Reporter:  Per|  Owner:  Per 
 Type:  defect | Status:  accepted
 Priority:  major  |  Milestone:  unspecified 
Component:  Engine: other  |Version:  svn/trunk   
 Keywords:  sensors teams  |   Operating_system:  All/Non-Specific
Blockedby: |   Blocking:  
---+
Changes (by Per):

  * owner:  => Per
  * status:  new => accepted


Comment:

 Why only for locked teams? I'm not sure about changing all asserts to
 assert_or_return - sometimes the extra conditional is not really worth it,
 but I'll look into this one.

-- 
Ticket URL: 
Warzone 2100 Trac 
The Warzone 2100 Resurrection Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone 2100 Trac] #636: Shared sensors among allies

[Warzone 2100 Trac]

#636: Shared sensors among allies
---+
 Reporter:  Per|  Owner:  
 Type:  defect | Status:  new 
 Priority:  major  |  Milestone:  unspecified 
Component:  Engine: other  |Version:  svn/trunk   
 Keywords:  sensors teams  |   Operating_system:  All/Non-Specific
Blockedby: |   Blocking:  
---+

Comment(by Buginator):

 Will this only be used for locked teams?

 Also, if this fails: ASSERT(object != NULL, "Invalid pointer");
 We will crash in a release build.  Perhaps change that to
 ASSERT_OR_RETURN?

 Oh, and you might want to add a assert check to make sure player is in
 range?

-- 
Ticket URL: 
Warzone 2100 Trac 
The Warzone 2100 Resurrection Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev