OpenKore / OpenKore/openkore

Avoid List not working as intended

Open
#3,794 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion enhancement feature request
Dominant language
Perl
Stars
1.5k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

  • Openkore version git:
    OpenKore what-will-become-2.1 ( version git:ebd0be1_2023-09-22 ctime:2023_06_03 )
  • Server:
    Private Server ((serverType kRO_RagexeRE_2015_11_04a))
  • Bug Report / Feature Request:
    Configured avoidList to respawn at save point and then disconnect for 3600 seconds if any job/character is in sight. As per the doc here when teleport is set to 2, kore will respawn and then disconnect,

Here is the avoid.txt :

# Same as above, but uses player jobs instead of names
# There is no disconnect on chat for this section.
# Examples:
# see https://github.com/OpenKore/openkore/blob/master/src/Globals.pm#L141
Novice              1 2
Swordsman           1 2
Mage                1 2
Archer              1 2
Acolyte             1 2
Merchant            1 2
Thief               1 2
Knight              1 2
Priest              1 2
Wizard              1 2
Blacksmith          1 2
Hunter              1 2
Assassin            1 2
Peco Knight         1 2
Crusader            1 2
Monk                1 2
Sage                1 2
Rogue               1 2
Alchemist           1 2
Bard                1 2
Dancer              1 2
Peco Crusader       1 2
Wedding Suit        1 2
Super Novice        1 2
Gunslinger          1 2
Ninja               1 2
Xmas                1 2
Summer              1 2
High Novice         1 2
High Swordsman      1 2
High Magician       1 2
High Archer         1 2
High Acolyte        1 2
High Merchant       1 2
High Thief          1 2
Lord Knight         1 2
High Priest         1 2
High Wizard         1 2
Whitesmith          1 2
Sniper              1 2
Assassin Cross      1 2
Peco Lord Knight    1 2
Paladin             1 2
Champion            1 2
Professor           1 2
Stalker             1 2
Creator             1 2
Clown               1 2
Gypsy               1 2
Peco Paladin        1 2
Super Baby          1 2
Taekwon         1 2
Star Gladiator          1 2
Flying Star Gladiator           1 2
Soul Linker         1 2

Given the avoid.txt above, kore should respawn to seeing any of the Jobs specified and then disconnect. After some testing, it seems kore disconnect out right without waiting to teleport/respawn,

i tried the following scenario:
Paladin 0 1
kore teleports on sight of a Paladin
Palading 1 1
kore disconnect without teleporting
Paladin 1 0
kore disconnects <~ this is correct scenario
Paladin 0 2
kore respawns to savepoint
Paladin 1 2
kore just disconnects without respawn first

I made sure it has fly wing, butterfly wing, or teleport skill.

I tested on Priest, High Priest with only skill, I also check with taekwon with fly wing and butterfly wing.

For some reason, ai_useTeleport(1) or ai_usetTeleport(2) was not called/finished before doing relog($config{avoidList_reconnect}, 1);
asdasdas

  • Summary:
    openKore outright disconnects with out performing teleport/respawn when configured to use avoid list:
    asdas111

teleportAuto_onlyWhenSafe is also set to 0 in config.txt
avoidList_inLockOnly is also set to 0 in config.txt

Not sure if the timeouts.txt teleport related numbers are affecting this, this is what is configured for mine:

ai_teleport 1
ai_teleport_away 3
ai_teleport_idle 4
ai_teleport_portal 2
ai_teleport_hp 3
ai_teleport_safe_force 120

ai_teleport_retry 0.5
ai_teleport_delay 0.5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the avoid.txt behavior and the avoid-list handling around ai_useTeleport(1), ai_useTeleport(2), and relog($config{avoidList_reconnect}, 1). Compare the Paladin scenarios against config.txt and the teleport-related entries in timeouts.txt. Done means teleport or respawn completes before disconnecting for the configured avoid-list cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.