Opened 12 years ago

Closed 11 years ago

#1651 closed enhancement (wontfix)

Minimum distance to enemy CCs.

Reported by: historic_bruno Owned by:
Priority: Should Have Milestone:
Component: UI & Simulation Keywords:
Cc: wraitii Patch:

Description (last modified by sanderd17)

It might have inherited this bug from qBot, but I have only noticed it with qBot-xp. Basically in the screenshot below several CCs are being built very close to eachother around a stone mine, which is not allowed by the minimum distance criteria (~180 game units). This limit applies even to newly placed foundations:

As noted in the comments, the AI isn't doing anything wrong. But the question is if we should be able to place foundations of CCs so close to each other, or if the 180 tiles distance should apply to all CCs, irregardless of the owner.

Attachments (1)

qbot-xp-ccs.jpg (155.1 KB ) - added by historic_bruno 12 years ago.

Download all attachments as: .zip

Change History (9)

by historic_bruno, 12 years ago

Attachment: qbot-xp-ccs.jpg added

comment:1 by historic_bruno, 12 years ago

Description: modified (diff)

comment:2 by wraitii, 12 years ago

I can confirm the limit are not enforced completely for qBot-xp, though I think it could be fairly easily changed.

It's trying to build 3 CCs around a stone mine, which however seems not normal, was it a scenario map? The AI should never build CCs unless the target is out of its territory, so this seems like a bug.

(from IRC: I noticed the cluster CCs from different AIs too, notably on RM Oasis. This happens because A] The AIs know about the whole map B] they check for enemy territory but not distance to CCs, so this can happen. AIs generally tend to be too promiscuous, I have an idea to fix that (keeping a "Danger map"), but this is not close to being implemented. As for the low-level enforcement of rules, I'm OK with that as long as warnings pop up. AIs can't really know if a placement failed for now (perhaps some specific events could be created to handle that).)

Last edited 12 years ago by wraitii (previous) (diff)

in reply to:  2 comment:3 by historic_bruno, 12 years ago

Replying to wraitii:

It's trying to build 3 CCs around a stone mine, which however seems not normal, was it a scenario map? The AI should never build CCs unless the target is out of its territory, so this seems like a bug.

It was the random map version of Saharan Oases.

There are actually multiple problems, one is the AI trying to build CCs so close, the other is that Commands.js should be checking build restrictions before it allows the foundation to be placed. Maybe there is a bug in CheckPlacement too?

comment:4 by historic_bruno, 12 years ago

After inspecting CheckPlacement, the distance build restriction is only checking a player's own entities, so qBot-xp isn't doing anything wrong. It still seems like a problem to be allowed to place so many CCs so close together :/

comment:5 by sanderd17, 11 years ago

Description: modified (diff)
Keywords: design added
Summary: qBot-xp ignoring distance build restrictions on CCs?Minimum distance to enemy CCs.
Type: defectenhancement

As the issue doesn't reflect the title or contents of the ticket anymore, I took the liberty to update it and add the 'design' keyword.

My personal opinion is that there is no problem, if players want to do this, they should be able.

comment:6 by Pureon, 11 years ago

wraitii and I discussed this ticket today and we agreed that this behavior should continue to be allowed - no minimum distance to enemy CCs should be added. The situation shown in the screenshot above is caused because AIs currently build within the FOW without first scouting the area - so it's the AI developer that should prevent this unusual behavior happening if needed.

comment:7 by Adrián Chaves, 11 years ago

I agree as well. Is anyone against closing this issue as “Won’t Fix”?

comment:8 by historic_bruno, 11 years ago

Keywords: design removed
Milestone: Backlog
Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.