• Breaks the limit for the amount of actors, classes, skills, items, weapons, armors, enemies, troops, states, animations, tilesets, common events, switches, variables, and elements you can include in your project.
  
• Gives you a notification on how long the database limit breaking process took.
  

1. Backup your Data folder, just to be on the safe side in case anything goes wrong.
   
2. Set the new max value for each data group.
3. Create an event and make it turn on [Doc4]'s conditional switch.
4. Run your project.
5. Press the Input Button set in PK8_DLB['button'] (Default: F7)
6. Close the Game.exe as soon as you're told it's done manipulating your project's data files.
7. Close your project WITHOUT SAVING.
8. Open your project again and the new database limits should be there.
   

• I'm trying to edit the switches beyond 5000 and it's not working!
  Not a question, but I get the idea. You'll need to head to the Game_Switches class of your script editor and modify two methods.
  First, replace the [](switch_id) method with this:
  
  Code:

  def [](switch_id)
    if @data[switch_id] != nil
      return @data[switch_id]
    else
      return false
    end
  end
  Next, you'll need to replace the []=(switch_id, value) method with this:
  
  Code:

  def []=(switch_id, value)
    @data[switch_id] = value
  end
• The same thing above applies to Game_Variables.
  Go to your Game_Variables class and replace [](variable_id) with this:
  
  Code:

  def [](variable_id)
    if @data[variable_id] != nil
      return @data[variable_id]
    else
      return 0
    end
  end
  Next, replace []=(variable_id, value) with this:
  
  Code:

  def []=(variable_id, value)
    @data[variable_id] = value
  end

(04-09-2012, 08:25 PM)Zackwell Wrote: That's a lotta variables. =o