search

codebackup / bwapi

Automatically exported from code.google.com/p/bwapi
0 stars 0 forks source link

Make cloaked unit detection more strict #436

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I discovered this week something I am not confortable with. Using BWSAL 
UnitGroup's commands, it is possible to collect a lot of information on enemy 
cloaked units even if you don't have any detectors.

You can find attached a screenshot where my dragoons are targetting a DT (red 
lines) even if I have no photon cannons / observers. In this very specific 
situation, I used the intruction SelectAllEnemy()( canAttack )( isCompleted 
).inRadius(...) to grab enemy units around my dragoons, and I can have the 
position of cloaked units. Thus, to attack them, a mere attack( 
cloaked_unit->getPosition() ) is possible, and I guess can be very efficient 
with explosive attacks (Reaver, for instance).

I think it should be fixed, because it becomes to easy then for an AI to handle 
enemy cloaked units without detectors. One can argue a human being can spot as 
well cloaked units thanks to the blur effect. That's right, but it remains more 
complicated and not so automatic than a simple SelectAllEnemy() instruction.

So, what do you think guys? Should BWAPI take this fact into consideration? 

To debate about it: http://www.broodwarai.com/forums/index.php?showtopic=998

Original issue reported on code.google.com by florian....@gmail.com on 18 May 2012 at 3:25

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 18 May 2012 at 4:23

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 7 Jan 2013 at 3:53

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 15 May 2013 at 7:55

GoogleCodeExporter commented 9 years ago 
The BWAPI project is slowly undergoing the migration to GitHub. All issues have 
been migrated to the GitHub issue tracker located here: 
https://github.com/bwapi/bwapi/issues

In order to receive updates on your issue, please head over to the GitHub issue 
tracker and subscribe to your issue.

Original comment by AHeinerm on 15 Apr 2014 at 7:46