Skip to content
The Chat Archive
gpt-4o-2024-08-06· OpenAI WildChat-4.8M (AI2)

Below is my code automacro checkmap { location not morroc location not paydun00 location…

  1. User

    Below is my code

    automacro check_map {
    location not morroc
    location not pay_dun00
    location not pay_dun01
    location not pay_dun02
    base > 35
    timeout 60
    
    call {
    do c @load
    pause 2
    do conf lockMap 0
    do move 160 99
    do talknpc 165 97 c r1 r16 c c r2 #edit
    do conf lockMap pay_dun02
    pause 2
    do eq Arrow
    do move 16 33
    release check_map
    }	
    }
    

    can you check if my code using openkore marco like this below

    location [not] <mapname [ [ ]] [, ...] Triggers when you are [not] at the specified location. When neither nor are given, it triggers when you are [not] on . When are not given, it triggers when you are [not] on at (,). When both and are defined it triggers when you are on somewhere between , (upper left) and , (lower right, where < and > Comma-separated arguments are treated as OR conditions: location geffen, prontera 123 234 Triggers when you are either in geffen or in prontera at 123 234. Multiple lines are treated as AND conditions: location not geffen location not prontera

  2. Assistant

    Your code is using OpenKore's automacro functionality with conditions and actions, and it seems to be attempting to check your character's location, base level, and implement certain actions based on these checks. Let's break down the code and check if it is doing what it's supposed to do given your understanding of the location conditions.

    1. Location Condition:

      Your code:

      location not morroc
      location not pay_dun00
      location not pay_dun01
      location not pay_dun02
      

      These lines are correctly set up to trigger the macro when your character is not in any of the specified maps (morroc, pay_dun00, pay_dun01, pay_dun02). Multiple lines are treated as AND conditions, which means that all of these conditions must be true (i.e., you are not on any of these maps) for the macro to trigger.

    2. Base Level Condition:

      base > 35
      

      This condition is correct for triggering the macro only when the character's base level is greater than 35.

    3. Timeout Condition:

      timeout 60
      

      This stipulates the minimum time (in seconds) that must pass since the last time this macro was executed before it can be triggered again.

    4. Call Block:

      call {
          do c @load
          pause 2
          do conf lockMap 0
          do move 160 99
          do talknpc 165 97 c r1 r16 c c r2 #edit
          do conf lockMap pay_dun02
          pause 2
          do eq Arrow
          do move 16 33
          release check_map
      }
      
      • do c @load: Executes the @load command, presumably to go to the save point.
      • pause 2: Pauses execution for 2 seconds.
      • do conf lockMap 0: Temporarily removes any lock map configuration.
      • do move 160 99: Attempts to move the character to coordinates 160, 99.
      • do talknpc 165 97 c r1 r16 c c r2 #edit: This is a sequence to talk to an NPC and navigate through the dialogue or menu options. The comment may indicate a note for editing.
      • do conf lockMap pay_dun02: Sets pay_dun02 as the lock map, restricting movement elsewhere.
      • do eq Arrow: Equips the character with an arrow, necessary for archers.
      • do move 16 33: Moves the character to specific coordinates (16, 33).
      • release check_map: Frees the macro, allowing it to be triggered again once conditions are met.

    In summary, your macro setup using OpenKore seems correct according to the provided guidelines and should work as intended, given no syntactical or logical errors are in place. Be sure to test it to confirm its correctness in your specific game environment.

  3. User

    Why my bot at payon_town with setting "do conf lockMap pay_dun00".

    This look like my bot dont even run my macro

  4. Assistant

    If your bot character is not executing the macro and moving to the map you've specified (pay_dun00), there could be several reasons why the macro is not being triggered or executed as expected. Here are some possible causes and troubleshooting steps:

    1. Macro Conditions Not Met:

      • Ensure that all the conditions you've set for the macro to trigger are indeed being met. For instance:
        • Is the character's base level truly greater than 35?
        • Is the character currently not on one of the specified maps (morroc, pay_dun00, pay_dun01, pay_dun02)?
    2. Macro Timing:

      • Confirm that the timeout condition is satisfied. If the macro has triggered recently, it won't trigger again until after 60 seconds.
    3. Syntax Issues:

      • Double-check your macro for any syntax errors or unintended typos that could prevent the macro from being recognized or triggered.
    4. Macro File Loading:

      • Ensure that your macro file is correctly loaded by OpenKore. If you made changes, restart OpenKore or reload the macros to apply them.
    5. Log and Debug:

      • Add some logging within your macro to see if it's attempting to execute, like do log "Macro triggered". This will help confirm if the issue is with triggering or with subsequent execution.
    6. Permission Settings:

      • Check if the lockMap setting is correctly allowing map changes. Ensure that any related configuration settings in OpenKore aren't interfering with map switching.
    7. Conflicts with Other Macros or Plugins:

      • Verify that no other macros or plugins are overriding the settings from this macro, or conflicting in a way that prevents its execution.
    8. Test in Isolation:

      • Temporarily comment out or simplify conditions to see if there’s a particular condition preventing execution. For example, try:
        automacro simple_check {
          location not payon
          call {
            do log "Basic macro triggered"
            release simple_check
          }
        }
        

    By systematically checking through these areas, you should be able to identify why the macro isn't running and ensure it functions as expected. Debugging macros can often require incrementally checking conditions and functionality to pinpoint the exact issue.