Opened 5 years ago

Last modified 4 years ago

#785 accepted defect

Pub Hunt Module

Reported by: SpookedOne Owned by: JoyRider
Priority: lowest Milestone: milestone:
Component: Bots - PubSystem/PubAutobot Version: Latest version from repository
Severity: blocking Keywords:
Cc:

Description

The hunt module for pubsystem is currently malfunctioning and has been disabled. Please review module for possible fixes or rewrite.

Change History (4)

comment:1 Changed 5 years ago by JoyRider

  • Owner set to JoyRider
  • Status changed from new to accepted

How is it currently broken?

comment:2 Changed 4 years ago by SpookedOne

Hope you're still around Joy. Not sure exactly, but I did notice concurrent modification exceptions being thrown after I tried to comment it out in PubContext.java.

comment:3 Changed 4 years ago by SpookedOne

  • Priority changed from normal to lowest
  • Severity changed from minor to blocking

comment:4 Changed 4 years ago by Trancid

Recent testing shows that the hunt module in itself is working ok enough. The flaw seems to be in the logic behind it, since the pub setup generally constitutes out of several large frequencies instead of individual frequencies. This can lead to the following situations, when applying the default hunt mechanics:

Hunt starts:
Player 1 (freq 0) -- hunts --> Player 2 (freq 1) -- hunts --> P3 (0) --> P4 (1) --> P1 (0).

Player 2 successfully hunts P3. Normally P3's target would be assigned to P2, but in this case, this would be P4, which is in the same frequency as P2. From what I recall from the tests, P2 actually doesn't get a new target assigned and is essentially deadlocked. P4 will have no hunter chasing him, making the game easier on him.

This unfortunately also messes up the winner/loser part of the pub hunt.

Note: See TracTickets for help on using tickets.