FearLess Cheat Engine

More Info: I used AssetStudio to extract the TextAssets from the games' unity assets. TextAssests 'contents' and 'system_en' were used to map ID's to locale names (this means if someone wanted to do it for jp or fr or whatever locales, you could use the corresponding system_locale). It's been a while, so I have no idea how I stumbled upon the right mono method, but because the games have all been written with similar codebase, the method 'Last.Data.DropItemData..ctor' is what determines drops. Simply turn on mono, and browse the memory view, Enumerate the symbols and goto the method by it's name. Every FF:PR title's method is slightly different, but the section of code that needs to be modified is the same. If the game updates, the method name should still exist, and the section of code should (hopefully) still be there - but the AOB scan uses parts of the code around it to locate it, which can change.

I'm sure this is pretty self explanatory for people who regularly create tables. But if your someone like me who gets just as frustrated as you about broken tables, and is willing play around a bit, I hope this helps.

This is going to be lengthy.

Script Usage
The TL:DR :
Main
Veldt Monster Party - Forces an encounter with a specific monster formation, no restrictions.
Alternate
Veldt Group - Forces an encounter with one of 64 monster groups, selected randomly from 8 monster subgroups. Game restrictions apply.
Veldt Subgroup - Forces an encounter with one of 8 monster subgroups, selected randomly from 64 monster groups. Game restrictions apply.

Veldt Group and Veldt Subgroup will work together - If you know the specific group and subgroup, then you can effectively pick a specific monster formation. The caveat is that game restrictions are in-place. If you never encountered the formation, then the game picks another encounter or just skips the encounter. This is useful for figuring out if you might have missed a formation, but also bad for the same reasons. Veldt Monster Party will force the encounter regardless if you've seen it or not. In addition, it has a side effect/bonus of adding that encounter as...one....of your....encountered....encounters.

note: Some might be wondering about the beastiary. The game records from all playthroughs, so if you are playing a second time or encountered an enemy and later died, it will be recorded in the beastiary but the enemy formation will not be recorded as encountered in your save file. Also - Beasiary is for enemies, Monster Parties is for formations.

Game Details
As a brief overview, the game has a record of every monster party encounter. This monster party is broken into 64 groups, with 8 monster party subgroup in each group. Without going into too much detail, the game rotates thru all 64 groups sequentially, and will randomly pick a subgroup as it's target encounter. There are restrictions, such as picking encounters you've only ever seen, as well as no bosses, and others - this is outside the scope of this discussion. Keep in mind that this is how it worked in all versions of the game, so we will be trying to locate a similar process.

Unity Files
I use Asset Studio to view the unity files in the game. When exploring, it's important to find what keywords the programmers were using to identify things such as monsters, monster formations, the veldt, etc. This is just something you discover when poking around.

serial_misc_assets - Hidden amongst other data in this file is a json list of veldt monster parties, known as 'beast_field_encounter_table'. It looks very similar to how it was in the actual game (64ish groups of 8ish, but not really due to aforementioned restrictions).

monster_party - This file lists data for how battles are set up, such as backgrounds and music....as well as ID's for up to 9 monsters.

monster - This file lists data on each monster, the most important is the ID's for localization names.

system_en - Our favorite file. This one localizes everything into english. There are system files for other languages if you want.

From this, we learn that the programmers refer to the veldt as 'beast', and the different monster formations as 'monster parties', and encounters as ...well 'encounters'.

Also, by combining this data, we can create a party table that uses monster names.

Cheat Engine/Mono
This process was the most difficult. We use the hints we found in the unity files to try to find the mono functions that refer to the veldt. A lot of the work was trial and error. Once you activate mono, you can search the methods/classes with keywords using dissect and .net info - and again, just poke around. A list of important methods/classes are below:

Last.Map.EncounterLot.CheckEncount - This is our main method used to determine if a battle will occur. All the scripts I wrote for the veldt are contained in this section.

Last.Map.Encount.BeastFieldEncount.SearchGroupId - This method is used in the first method to pick the next monster group. How it does it is unimportant, but it returns a number correlating to the monster group.

UnityEngine.Random.Range - This method is used in the first method. It is general purpose, but for this specific case it is used to pick a number from 0 to 7 (1-8) correlating to the monster subgroups in each group.

Alternate Scripts
So now we have the Veldt Groups and Veldt Subgroups. Originally, this worked well, until I found out that this doesn't let you encounter formations you've never seen. The side effect of this is that if you haven't seen an encounter, then the selected Veldt Group and/or Veldt Subgroup will pick another encounter (usually the next one) or just...not encounter anything at all. I wanted to force the encounter whether I had seen it or not.

Cheat Engine
You could also find the Veldt Group by scanning memory. But, for reasons I'm not entirely sure on, it doesn't seem to work for Veldt Monster Party. The next best solution I could do was use breakpoints after Veld Groups and Veldt Subgroups to find the first instance of a value referring to Veldt Monster Party in the registers. I found it about 24 lines after the UnityEngine.Random.Range.

Main Script
Ok, there really isn't any further explanation here. The script forces a specific encounter and as a side effect/bonus, adds it to your encountered list, so even Veld Groups and Veldt Subgroups work after that. But why would you need them anymore?

All that needed to be done after this was to actually make a drop down list that makes it a bit more clear what the encounters actually are. Remember how I said we could combine the unity data to make a party table with names? Toss that into a google sheets doc, do some manipulation, and spit out the results into a drop down list. Now you can see what the encounters are instead of ID's.

Final
As always, the reason I leave this here is multifold:
1. You are free to use these scripts for your own table. Credit is nice, but I honestly could care less.
2. If something is broke and I am unavailable, it might help you find out how I did things, and maybe you can fix it yourself.
3. I'm learning, so maybe this will help you learn too.
4. This isn't optimized at all. Maybe someone will want to adopt it and make it all pretty. Add bells and whistles and all that. Go for it.