You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Baconbowl's cap 3 poses an interesting challenge because it doesn't appear to have any player trigger, just a world trigger.
The i_t_g for both cap 1 and cap 2 have "netname" "Capture Point 1" which is weird but at least it shows up as the appropriate player trigger in the logs, for example: L 08/30/2022 - 10:32:28: "hello? Nomad [BOISY] pls<3><STEAM_0:1:5107><#Dustbowl_team1>" triggered "Capture Point 1"
Cap 1 and cap 2 also have b_b values which are logged as world triggers, for example: L 08/30/2022 - 10:32:28: World triggered "#dustbowl_blue_secures_two"
However, the cap 3 i_t_g does not have a netname and doesn't log any player triggers.
Cap 3 has "target" "cap3" which is a multi_manager, which has... "win_message" "1"
The info_tfgoal with "targetname" "win_message" has "b_b" "#dustbowl_blue_caps" which is the only thing we see in the log when someone captures point 3, for example: L 08/30/2022 - 10:34:50: World triggered "#dustbowl_blue_caps"
It's possible I am just dumb, but it seems to me like this problem shouldn't exist if the map entities were fixed, and maybe an entity edit is the ideal solution.
With that said, is it possible to solve this problem in hampalyzer?
Is there a better way than waiting for that #dustbowl_blue_caps" world trigger, then looking back at who triggered "Flag 3" most recently?
Besides this problem, there should only be a couple of parse cases that need to be added to finalize baconbowl support:
case "#dustbowl_five_minutes_left": // baconbowl
case "#dustbowl_four_minutes_left": // baconbowl
case "#dustbowl_three_minutes_left": // baconbowl
case "#dustbowl_two_minutes_left": // baconbowl
case "#dustbowl_sixty_seconds_left": // baconbowl
case "#dustbowl_thirty_seconds_left": // baconbowl
case "#dustbowl_blue_secures_one": // baconbowl (already handled by "Capture Point 1")
case "#dustbowl_blue_secures_two": // baconbowl (already handled by "Capture Point 1" - same name as cap1)
(all in the Ignore bucket for world triggers, near parser.ts lines 945-993)
Baconbowl's cap 3 poses an interesting challenge because it doesn't appear to have any player trigger, just a world trigger.
The i_t_g for both cap 1 and cap 2 have
"netname" "Capture Point 1"
which is weird but at least it shows up as the appropriate player trigger in the logs, for example:L 08/30/2022 - 10:32:28: "hello? Nomad [BOISY] pls<3><STEAM_0:1:5107><#Dustbowl_team1>" triggered "Capture Point 1"
Cap 1 and cap 2 also have
b_b
values which are logged as world triggers, for example:L 08/30/2022 - 10:32:28: World triggered "#dustbowl_blue_secures_two"
However, the cap 3 i_t_g does not have a
netname
and doesn't log any player triggers.Cap 3 has
"target" "cap3"
which is a multi_manager, which has..."win_message" "1"
The info_tfgoal with
"targetname" "win_message"
has"b_b" "#dustbowl_blue_caps"
which is the only thing we see in the log when someone captures point 3, for example:L 08/30/2022 - 10:34:50: World triggered "#dustbowl_blue_caps"
It's possible I am just dumb, but it seems to me like this problem shouldn't exist if the map entities were fixed, and maybe an entity edit is the ideal solution.
With that said, is it possible to solve this problem in hampalyzer?
Is there a better way than waiting for that
#dustbowl_blue_caps"
world trigger, then looking back at who triggered"Flag 3"
most recently?Example games:
http://app.hampalyzer.com/parsedlogs/OldSchool-2022-Aug-27-06-24/ (no cap 3 because red successfully defended)
http://app.hampalyzer.com/parsedlogs/OldSchool-2022-Aug-27-06-51/ (Suicide_Kid captures point 3 but the only indication of this in the log is
World triggered "#dustbowl_blue_caps"
)Example log files:
baconbowl_r-R1-L0827017.log
baconbowl_r-R2-L0827019.log
L0830046.log (log from me finishing the map by myself in an empty server)
Entity definitions:
baconbowl_r.ent.txt
The text was updated successfully, but these errors were encountered: