COELOCANTH'S PROFILE

coelocanth

5448

Search

Filter

[SCRIPTING] [RMVX ACE] Turning Switch on Ambush\Preemptive battles

05/09/2021 07:15 PM

The common event I want occurs after battle though.

Yes, unfortunately parallel / autorun common events activated by switches only run on the map.
You'll need a troop event, or a script that allows you to use common event(s) as troop events.

A troop event can call a common event with no problems, so worst case you could add an event to every troop that calls common event X - and in common event X check the switches you're interested in and call common events Y,Z...

Mapdaptation

05/08/2021 12:18 PM

I'd thought you would be merging all the 2k3 maps into a single 2k3 game, all the MV maps into a single MV game, etc.

Mapdaptation

05/08/2021 09:51 AM

Two questions:

1. Does the single download collection mean only open tilesets (not requiring projects to be encrypted) can be used?
2. Are long narrow maps (like 13x60) allowed? i.e. is the 25x25 a minimum number of tiles, or a requirement for maps to scroll in both directions?

[SCRIPTING] [RMVX ACE] Turning Switch on Ambush\Preemptive battles

05/08/2021 09:41 AM

Hi Porkate42,

You're on the right track, but you may have mixed up some MV scripting.

First step, we want to call the original on_encounter code to set those random values.
The simple method is to simply copy the code into your redefined function:

module BattleManager
  #--------------------------------------------------------------------------
  # * Processing at Encounter Time
  #--------------------------------------------------------------------------
  def self.on_encounter
    @preemptive = (rand < rate_preemptive)
    @surprise = (rand < rate_surprise && !@preemptive)
    # TODO: add new code
  end
end

But that way leads to compatibility problems if more than one script modifies the same function.

So instead we should alias and monkey patch like this:

module BattleManager
  #--------------------------------------------------------------------------
  # * Processing at Encounter Time
  #--------------------------------------------------------------------------
  class << self
    alias on_encounter_pes on_encounter
  end
  def self.on_encounter
    self.on_encounter_pes
    # TODO: add new code
    print(@preemptive)
  end
end

The alias is a bit more complicated than usual, because we're working with a module. For regular classes not using the "self.method", the aliasing would look like this:


class Game_CharacterBase

  alias ccss_move_straight move_straight;

  def move_straight(d, turn_ok = true)

Finally, you want to store the @preemptive and @ambush values in switches.
This is where you seem to have mixed in some MV style code.
In VX ace, it's much simpler: $game_switches can be accessed as if it were an array:

$game_switches[431] = true

But, @preemptive is already the right type, so we can store directly in the switch:

module BattleManager
  #--------------------------------------------------------------------------
  # * Processing at Encounter Time
  #--------------------------------------------------------------------------
  class << self
    alias on_encounter_pes on_encounter
  end
  def self.on_encounter
    self.on_encounter_pes
    $game_switches[431] = @preemptive
    $game_switches[432] = @ambush
  end
end

I'm not sure if this is important to note but I'm using on map battles through events.
You could in this case set the switches via event commands...
But you'll probably need to call BattleManager.on_encounter in a script call before battle processing, as it's normally only used for random encounters IIRC.

1.44 Floppy Disc Event

05/08/2021 02:22 AM

Classic RPGs

Unchained(Decky)

COELOCANTH'S PROFILE

Search

Filter

Submitted Items