Jump to content
  • Instance entry level not correct...

    • Status: Completed
      Main Category: Script (Eluna / SD3)
      Sub-Category: instancehandling
      Version: 21.2 Milestone: 22 Priority: Normal
      Implemented Version: 21.3

    Cannot enter certain instances...

    While going through the quests and finding incorrect dialogue or other text/emotes, I found a strange bug. Scarlet Monastery is saying I need to be 31 to enter on my 29 rogue. On my 33 hunter it says I need to be 35. It allows my 36 hunter in. This is not correct. Here is the dump for SM (map 189) from the database.
    MariaDB [zero_world]> SELECT * FROM `instance_template` WHERE `map` = 189;
    | map | parent | levelMin | levelMax | maxPlayers | reset_delay | ghostEntranceMap | ghostEntranceX | ghostEntranceY |
    | 189 | 0 | 29 | 48 | 10 | 0 | 0 | 2892.24 | -811.264 |
    1 row in set (0.00 sec)
    That is still a tad high, according to historical documents referenced below, but a 29 rogue or 33 hunter SHOULD be able to enter based on the minimum level specified. I cannot even summon a group-member below 35 into the instance with me. They get the "must be 35 to enter" message. What's weird is that it tells my rogue 29 but tells my hunter 35. Odd as heck!


    User Feedback

    Recommended Comments

    SELECT id,`name`,required_level FROM areatrigger_teleport WHERE target_map=189;

    45,Scarlet Monastery - Graveyard (Entrance),29
    610,Scarlet Monastery - Cathedral (Entrance),35
    612,Scarlet Monastery - Armory (Entrance),33
    614,Scarlet Monastery - Library (Entrance),31

    Well, some idea is seen here, but I cannot say, is it wrong.

    Link to comment
    Share on other sites

    However, this mechanic does not explain a weird implementation bug with double call to Player::TeleportTo() due to delayed teleporting. For this particular instance, several entry ATs are defined. The 1st call returns OK for level 29, but the 2nd call finds an unpredictable AT from the fourth ones, depending on the DB entries order.

    The bug has the most beatiful look in such case: 1) as a non-GM 29 lvl character, try to enter the enabled - left for 29 lvl - teleport; 2) get "Required level 35" error; 3) go away from the instance entrance; 4) .gm on will now teleport you into the instance.

    Link to comment
    Share on other sites

    Using GM mode will teleport you into anything, even Onyxia at level 1 and without the item required. A side-effect of this bug is that if a player, say level 30, attempts to enter SM and cannot, I cannot teleport them as a GM anywhere. For example, I could not teleport my fiance from the instance-gates for SM back to Brill. It says the player is already being teleported even though she was not. The only fix is for her to log and come back. It is kind of like a teleport flag is permanently set.

    Link to comment
    Share on other sites

    You did miss a point in the algorithm above.
    [quote=Olion]3) go away from the instance entrance;[/quote]
    Anyway, these both are due to a single implementation bug, namely a jammed delayed teleport. @H0zen has fixed it [URL="https://github.com/mangoszero/server/pulls"]here[/URL].

    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use