Skip to content

Check automacros again if macro ended this AI cycle #4169

@Henrybk

Description

@Henrybk

Describe the solution you'd like

When a macro ends it can sometimes leave open an AI spot for other things to trigger until the next AI cycle, maybe we should check automacros again before letting this happen, as it can lead to bugs bellow where this split second triggered a route to lockmap which triggered an NPC talk which was interrupted by the macro, crashing both talknpc and macro

[2025.07.21 15:09:47.82] [eventmacro message] [baseMacro] End
[2025.07.21 15:09:50.35] Calculating route to: Arredores de Prontera (5)(prt_fild05): 290, 224 (Distance: 4)
[2025.07.21 15:09:35.35] Talking with NPC Kafra Employee (6) at (156,97), ID E4 13 00 00, sequence 'r~/(Warp|Teleport)/i r~/Prontera/i'
[2025.07.21 15:09:49.18] [eventMacro] Conditions met for automacro 'set_savemap_variables', calling macro 'automacro_set_savemap_variables_call_block'
[2025.07.21 15:09:49.25] [eventmacro message] [set_savemap_variables] lockMap_bound_saveMap_kafra_map is prt_fild05
[2025.07.21 15:09:50.31] [eventMacro] Conditions met for automacro 'moveLocKafraOutside', calling macro 'move_to_near_kafra '
[2025.07.21 15:09:50.99] NPC image: kafra_05.bmp
[2025.07.21 15:09:50.99] Kafra Employee: [Kafra Employee]
Welcome. Kafra is always with you.
How may I help you today?
[2025.07.21 15:09:51.91] ------ Responses (Kafra Employee) ------

Response

0 Save point.
1 Use Storage.
2 Teleport.
3 Rent a cart.
4 Check other info.
5 Quit.
6 Cancel Chat

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions