• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Our friends from the Johto Times are hosting a favorite Pokémon poll - and we'd love for you to participate! Click here for information on how to vote for your favorites!
  • Cyndy, May, Hero (Conquest), or Wes - which Pokémon protagonist is your favorite? Let us know by voting in our poll!
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.
    Register

Bizarre "notice player" behavior

Firewheelies

Firewheelies

    • 4
    Posts
    7
    Years
    [EDIT] The issue has been resolved, it was an issue with Marin's Overworld Shadows script. Thanks Sparkin!

    Hello! I'm new here, and having a bit of a problem getting trainers to notice the player in v17 essentials.
    I set up Trainer(x), Kernel.pbNoticePlayer(get_character(0)), and set it to event touch. Yet, for some reason, the trainer will not approach the player. The battle will only start if the player walks directly into the NPC.

    The most bizarre thing about this is that this only happens sometimes. At complete random, the script runs properly and the trainer notices the player and approaches. I thought it fixed itself, but it started happening again and now I'm here. I haven't modified any scripts relating to noticing the player. Maybe I'm missing something?

    [PokeCommunity.com] Bizarre "notice player" behavior

    (This trainer was copied almost directly off of base essentials route 3, it doesn't work on route 3 either)
     
    Last edited:
    Hello, check the event name; " Trainer(2)" .
    Have you tried to change the number to something higher?
    E.g. "Trainer(4)". Each number corresponds to the amount of tiles
    the trainer events uses to "notice" the player. So if you set it to 2,
    you will need to be 2 tiles close to the trainer event in order for it to notice you.
     
    I've tested it in a clean version of Essentials and it works just fine. It must be some script that's interfering with it
     
    AenaonDusky said:
    Hello, check the event name; " Trainer(2)" .
    Have you tried to change the number to something higher?
    E.g. "Trainer(4)". Each number corresponds to the amount of tiles
    the trainer events uses to "notice" the player. So if you set it to 2,
    you will need to be 2 tiles close to the trainer event in order for it to notice you.
    Click to expand...

    Yeah I've attempted this, the trainer still ignored the player unfortunately. Thank you, though!

    Sparkin said:
    I've tested it in a clean version of Essentials and it works just fine. It must be some script that's interfering with it
    Click to expand...

    I have a feeling this is probably the issue as well. I have quite a few scripts installed through the Universal Plugin Installer and other sources. I'll go through and disable each one to see if anything causes it to start working again.
     
    Then that's it.
    The best thing when installing new scripts/plugins etc, is to avoid installing them all together.
    Do it one at a time and test various things.

    Now, in your case, maybe you have a script that interferes with 1) special tiles, 2) tile passability 3) scripts for older or newer versions of Essentials, 4) Anything that might mess event interaction...
    Sorry I couldn't help you more!
     
    Very true! I plan to be more careful from now on and test more before tossing scripts in. I think the culprit could be a terrain SFX script I installed. I don't think anything else I installed messes with tiles. It works, but it wasn't designed for essentials.

    I've also disabled one at a time and am still having the issue. I didn't start new save files before hand though, I don't know if that effects anything. I've seen the game act oddly sometimes if I change something without starting a new save. I'll try that, and if that fails, I'll install each script one by one into a fresh copy of essentials and see if I run into problems.
     
    Firewheelies said:
    Very true! I plan to be more careful from now on and test more before tossing scripts in. I think the culprit could be a terrain SFX script I installed. I don't think anything else I installed messes with tiles. It works, but it wasn't designed for essentials.

    I've also disabled one at a time and am still having the issue. I didn't start new save files before hand though, I don't know if that effects anything. I've seen the game act oddly sometimes if I change something without starting a new save. I'll try that, and if that fails, I'll install each script one by one into a fresh copy of essentials and see if I run into problems.
    Click to expand...

    Have you tried checking an "OverworldShadows" script?
     
    You must log in or register to reply here.
    Back
    Top