HELP - Contestable Control Points; Engine Limitations?

Posted this to the discord without much response (PST problems), so I figure I'll put it on here.

This is in relation to ctf_mimosa, which uses a custom gamemode where the flags are captured at the center of the map. To balance out the center capture I added timed capture through control points, which is where the problems arise.

Just to be clear, when I talk about contestable I mean that the point capture can be blocked by the enemy team standing on the point. I used bots to check all of the below info.

Current iteration (A5):

Here is the HUD, which will help me better describe what's going on.

I've got 6 control points:

• Indexed 0-5
• Organized [5 4 3 0 1 2]
  • Setup to match the static flag trackers that are created by tf_logic_hybrid_ctf_cp

Currently, all points are neutral, however per the trigger_capture_area keyvalues, only red can capture 0-2 and only blu can capture 3-5. Additionally, the points are sequenced (hence the locks), so 0>1>2 and 3>4>5.

Only index 0 is contestable in this setup.

Test cases:
ctf_mid_test4.vmf (see attached)

• Changes to entity setup:
  • Set ownership to the respective defenders (3-5 are owned by red, 0-2 are owned by blu)
• Indexes 3-5 are contestable
• Index 1 is contestable
• Indexes 0 & 2 are not contestable

ctf_mid_test_1sided.vmf (see attached)

• Changes to entity setup:
  • Deleted points 3-5 and their associated capture areas and red flag
  • Restricted blu from winning in the team_control_point_master
  • If I set ownership of the points to blu:
    • Indexes 0-2 are contestable
      • Similar to a regular adctf setup, it works normally
  • If I set ownership of the points to neutral:
    • Index 0 is contestable
    • Indexes 1 & 2 are not contestable

Therefore, the sequential setup is otherwise working and blu ownership shouldn't affect the contest-ability.

I scanned over standin's control point setup (three neutral control points), and they all point to themselves for the "previous point required" keyvalue, so I'm not sure why index 3 isn't contestable when neutral. Otherwise I would have said that it was an issue with the neutral points.

I currently have no idea why indexes 0 & 2 aren't contestable in test4 because that makes no sense.

So,
calling all ent-wizards! What haven't I tried? What am I missing? Any ideas for work arounds?

Indexes, indices? Ibexes, ibices?

Bumping this for some more views, but also got some new information.

New test cases:
ctf_mid_test5.vmf (see attached)

• Changes to entity setup:
  • Removed 3rd point for both red/blu
  • Fixed up the indexing to compensate
  • If I set ownership of the points to neutral:
    • Index 0 is contestable
    • Indexes 1-3 are not contestable
    • Game isn't winnable, not too important to the fact finding mission
  • If I set ownership of the points to the respective defenders:
    • All indexes are contestable

Part of me thought this was a hard coded limitation to do with the number of contestable points available to both teams (though my points aren't truly contestable by both teams do to the settings in the trigger_capture area). It would make sense that less than 6 would be functional as needed with 5CP.

ctf_mid_test6.vmf (see attached)

• Changes to entity setup:
  • If I remove the 6th point from red:
    • Indexes 1, 3, & 4 are contestable
    • Indexes 0 & 2 are not contestable
  • If I remove the 6th point from blu:
    • All indexes are contestable

So not exactly right. It seems like blu is incapable of having a 3rd point, however ctf_mid_test_1sided indicates the opposite. Therefore, the issue is that blu cannot have a contestable 3rd point WHILE red also has contestable points.

At this point do I ping Jill? Anyone have other ideas for test cases? Has anyone tried 7CP?