Pearl ABS issues (bullets passing through walls & shield behaving oddly)

[Hammerklavier]

Hello,

I'm attempting to use the Pearl ABS scripts for RPG Maker VX Ace. Mostly, it works really nicely, but as I've played around with it over the past few months, I've noticed two significant issues. I'm hoping that these are simply due to my misuse of the scripts rather than an innate flaw.

1) When I use a projectile, such as a gun weapon or a magic spell, it invariably passes through everything, including walls. Since being able to hide behind walls is a significant strategy when dealing with projectiles, this is somewhat of a deal breaker at the moment. I've changed the "through" setting in the notes for the weapon, which allows the CPU bullets to behave correctly, but my own bullets, though they correctly stop after hitting something, don't end up causing any harm to my enemy targets. Any ideas on how to make this work?

2) When I use the shield, I'm finding that it works perfectly when I'm facing my target, but if I face a different direction, the enemies attacks just result in 0 damage. I'm not getting the "blocked by a shield" sound effect, just a bunch of 0's as though the enemy were missing me altogether. The shield should only work if I'm facing my target; I don't want it to allow total immunity to damage from all directions.

Is anyone else encountering these issues?

Thanks for any assistance with this.

 

[Sugor]

Maybe your didn't update? i think there's update for that not really into vx ace but i really think there should be an update for that.

 

[Sixth]

There is a shielding bug in the default Pearl ABS scripts, the one you mentioned. My Bugfixes for Pearl ABS script fixes that along with several other issues I found in that ABS, and it also adds some new, optional features. You can find that script on my pastebin.
Please read the instructions and setting details in that script, because I will NOT answer THAT question EVER again. Sorry, couldn't keep it inside.

The first issue is a valid issue too, and I made a workaround snippet for that too some time ago. No idea where I posted it though (probably posted it multiple times on different forums already, but forgot where), so I will just post it here too:

Spoiler

module ToolRestrict
 
  # Add any impassable region IDs for tools here.
  Regions = [40]
 
end

class Projectile < Game_Character
 
  def passable?(x, y, d)
    return false if tool_region_forbid?(x, y, d)
    return super(x, y, d)
  end
 
  def tool_region_forbid?(x, y, d)
    case d
    when 1; region = $game_map.region_id(x-1, y+1)
    when 2; region = $game_map.region_id(x+0, y+1)
    when 3; region = $game_map.region_id(x+1, y+1)
    when 4; region = $game_map.region_id(x-1, y+0)
    when 5; region = $game_map.region_id(x+0, y+0)
    when 6; region = $game_map.region_id(x+1, y+0)
    when 7; region = $game_map.region_id(x-1, y-1)
    when 8; region = $game_map.region_id(x+0, y-1)
    when 9; region = $game_map.region_id(x+1, y-1)
    else;   region = 0
    end
    return ToolRestrict::Regions.include?(region)
  end
 
end

You can put this snippet anywhere below the Pearl ABS scripts.
Just insert the region IDs which should block projectiles into the setting array, and mark your walls with those regions. No tool will be able to pass the marked tiles.
Ohh, and make sure to keep the Tool Through notetag on true for all tools, otherwise (as you already noticed) they won't deal any damage.

 

[Hammerklavier]

Wow, thanks Sixth!

I've tried both scripts. The projectile script is working nicely, no issues so far!

Unfortunately, I guess I'm "that guy" when it comes to the general bug fix issue that is intended to fix the shield issue, among other things. I tracked down a script from the pastebin.com, "[ACE] Bug Fixes for Falcao's Pearl ABS Liquid v3" version 2.2 and placed it below the other Falcao Pearl scripts (but above "Main"), but none of the keyboard commands for Pearl ABS are working for me anymore.

Reviewing the documentation, I'm not seeing the answer yet, but between your email and the opening paragraphs of the script that emphatically implore me to read all of the documentation carefully, I'm hesitant to pop the question here in case it is "THAT question". You've suggested that you won't answer it here, but can you at least confirm for me that (1) I have the correct and most up-to-date version of the code, and (2) this question is addressed in the script comments somewhere? I'm sure it's not a bug, just something I'm screwing up or missing.

 

[Hammerklavier]

Aha! Found it on lines 564 and 565. Switches 29 and 30 needed to be activated.