Borderlands 2 / The Pre-Sequel BPD/Kismet Graphs

Just a page to generate graphs from Borderlands 2/TPS BPDs and Kismets. If you don't know what a BPD or Kismet is, this probably isn't for you, but you can check out some basic information at the BLCMods Wiki. Many thanks to LightChaosman for the data which powers this generator!

Generate A Graph

Note: PNG graphic output supports a max. width of about 32k pixels. Graphics which would be larger than that will scale down, sometimes into illegibility. Stick with SVG output for extremely large graphs.

Borderlands 2 The Pre-Sequel SVG PNG

Optional:

Selecting a level here will allow the tree to follow Kismet sequence events within the specified level.

BL2 - Ardorton Station BL2 - Arena (final boss) BL2 - Arena BL2 - Arid Nexus - Badlands BL2 - Arid Nexus - Boneyard BL2 - Backburner BL2 - Badass Crater Bar BL2 - Badass Crater of Badassitude BL2 - Beatdown BL2 - Bloodshot Ramparts BL2 - Bloodshot Stronghold BL2 - Bunker BL2 - Burrows BL2 - Candlerakk's Crag BL2 - Caustic Caverns BL2 - Control Core Angel BL2 - Dahl Abandon BL2 - Dark Forest BL2 - Dragon Keep BL2 - Dust BL2 - End of the Line BL2 - Eridium Blight BL2 - Fallen Helios BL2 - Fight for Sanctuary BL2 - Fink's Slaughterhouse BL2 - Flamerock Refuge BL2 - Forge BL2 - Fridge BL2 - Friendship Gulag BL2 - Frostburn Canyon BL2 - Gluttony Gulch BL2 - H.S.S. Terminus BL2 - Hallowed Hollow BL2 - Hatred's Shadow BL2 - Hayter's Folly BL2 - Hero's Pass BL2 - Highlands Outwash BL2 - Highlands BL2 - Holy Spirits BL2 - Hunter's Grotto BL2 - Immortal Woods BL2 - Lair of Infinite Agony BL2 - Leviathan's Lair BL2 - Lynchwood BL2 - Magnys Lighthouse BL2 - Marcus's Mercenary Shop BL2 - Mines of Avarice BL2 - Mt. Scarab Research Center BL2 - Murderlin's Temple BL2 - Natural Selection Annex BL2 - Oasis BL2 - Opportunity BL2 - Ore Chasm BL2 - Paradise Sanctum BL2 - Pyro Pete's Bar BL2 - Raid on Digistruct Peak BL2 - Rotgut Distillery BL2 - Rustyards BL2 - Sanctuary (post liftoff) BL2 - Sanctuary (pre liftoff) BL2 - Sanctuary Hole BL2 - Sawtooth Cauldron BL2 - Scylla's Grove BL2 - Southern Raceway BL2 - Southern Shelf - Bay BL2 - Southern Shelf BL2 - Southpaw Steam + Power BL2 - Terramorphous Peak BL2 - Thousand Cuts BL2 - Three Horns Divide BL2 - Three Horns Valley BL2 - Tundra Express BL2 - Unassuming Docks BL2 - Vault of the Warrior BL2 - Wam Bam Island BL2 - Washburne Refinery BL2 - Wildlife Exploitation Preserve BL2 - Windshear Waste BL2 - Winged Storm BL2 - Writhing Deep BL2 - Wurmwater TPS - Abandoned Training Facility TPS - Cluster 00773 P4ND0R4 TPS - Cluster 99002 0V3RL00K TPS - Concordia TPS - Cortex TPS - Crisis Scar TPS - Deck 13 1/2 TPS - Deck 13.5 TPS - Eleseer TPS - Eye of Helios TPS - Helios Station TPS - Holodome TPS - Hyperion Hub of Heroism TPS - Jack's Office TPS - Lunar Launching Station TPS - Meriff's Office TPS - Motherlessboard TPS - Nexus TPS - Outfall Pumping Station TPS - Outlands Canyon TPS - Outlands Spur TPS - Pity's Fall TPS - Regolith Range TPS - Research and Development TPS - Serenity's Waste TPS - Stanton's Liver TPS - Sub-Level 13 TPS - Subconscious TPS - Titan Industrial Facility TPS - Titan Robot Production Plant TPS - Triton Flats TPS - Tycho's Ribs TPS - Veins of Helios TPS - Vorago Solitude
Allow following Kismet events through class boundaries

Optional:

Include Kismet variables in graphs (can lead to very busy graphs, but is generally useful)

Warning: The Kismet graphing abilities seem pretty solid to me, but I wouldn't be surprised if there are edge cases I've missed. Please let me know if any graphs error out, or are doing anything weird!

Option Reference

For the most basic functionality (which is all most people are ever going to need), simply paste the BPD name into the main textbox, choose the game, and hit "Generate." As of August 13, 2018, you can also put in a Kismet sequence start point to graph those. For instance, some valid start points:

• GD_Shields.Skills.Impact_Shield_Skill:BehaviorProviderDefinition_0
• Xmas_Dynamic.TheWorld:PersistentLevel.Main_Sequence.SeqEvent_RemoteEvent_16

The graph should let you know whenever it would "call out" to an external event, whether it's to another BPD or a Kismet sequence. In some cases, it can know the BPD name to display, in which case it will show you (see the screenshot below). By default, it won't actually "follow" any of these links, though.

In order to have the graph follow into event links as much as possible (which will often be into Kismet sequences), choose a level in which the BPD or Kismet will be running. This way, the grapher can know which Kismets are available to link to.

Finally, when graphing into Kismets, sometimes the sequence links will take the grapher out of the class that it started in. For instance, the graph of Distillery_Boss.TheWorld:PersistentLevel.Main_Sequence.SeqEvent_LevelLoaded_1 starts out in the main class Distillery_Boss.TheWorld:PersistentLevel.Main_Sequence. So long as Rotgut Distillery is chosen as the level to work in, the tree will end up showing that it branches out to other sequences into classes such as Distillery_Mission3.TheWorld:PersistentLevel.Main_Sequence. In order to actually follow those links, rather than just stopping at the class change, check the "Allow following Kismets through class boundaries" checkbox.

Output Reference

Green nodes are the initial Events in EventData2 which kick off the BPD trees. The number in brackets is the index in the BehaviorSequences array which the event lives. If the main BehaviorSequence has a name, it will be here. The Event name itself is always shown after a period. The second index in brackets is the index of the event inside the EventData2 index.

Blue nodes are Kismet sequence objects, and the darker blue, square-corner ones are Kismet sequence events. The lighter blue nodes are other sequence objects. The event name will be included where relevant.

Other nodes are behaviors from the BehaviorData2 array. The number in brackets is the index of the behavior.

Inbetween the behavior name and the optional variables (see below), there may be some extra data provided, depending on the behavior type. Most behavior types won't report anything special, but a few will. I am open to suggestions as to more data which would be usefully provided in the graph.

Variables are inside the nodes, underneath the title of the node. Output variables are prefixed by Out:, input variables are prefixed by In:, and context variables are prefixed by Ctx:.

• The left-hand side of the variable (before "via") is the relevant entry in the VariableData array, with its index in brackets. If the VariableData entry is named, the name will appear there as well. The data type is always shown.
• The right-hand side of the variable (after "via") is two components:
  • First, the relevant entry in the ConsolidatedVariableLinkData array, with its index in brackets. The name will always be shown there.
  • Secondly (after the comma), the index in the ConsolidatedLinkedVariables array which points to the actual variable.

The links between the behaviors will have a few labels attached right where they leave their parent node. The first number is the order in which they are called, starting with zero. The second number, in brackets, is the index of the ConsolidatedOutputLinkData entry being used to provide the link. The third line will be the "Link ID." Some Behaviors will require certain IDs for the links to work properly, so this should give you a feel for what the IDs are. (See my BPD Number Calculator page for information on how those relate to the values you'll see in the BPDs themselves.) Then, an optional fourth entry may appear under that, prefixed with a lowercase "d", which will specify a delay before triggering the next behavior.

Links which refer back to events will be colored in green if it's heading towards a BPD Event, or blue if it's heading towards a Kismet sequence event. If a RemoteCustomEvent links to an event name which isn't present in this BPD, the link will be shown in a node which looks a bit like an arrow pointing to the right. Those nodes will be light red for event names which appear to be invalid generally, and gold for events which explicitly link to other BPDs.

"Broken" BPDs

As of the newest DLC update (Commander Lilith and the Fight for Sanctuary), the data for six specific BPDs is partially missing, and prevents them from being graphed. This is because some BPD subobjects are apparently dynamically-named, and the number suffix can vary depending on when the level is loaded, so the dumps don't include those objects anymore. I currently don't really have any plans to fix this, but just for reference, here are the broken BPDs:

• GD_Orchid_CrystaliskAqua.Character.AIDef_Orchid_CrystaliskAqua:AIBehaviorProviderDefinition_1
• GD_Orchid_CrystaliskAqua.HitRegions.HitRegion_B_FootCrystalAqua:BehaviorProviderDefinition_0
• GD_Orchid_CrystaliskAqua.HitRegions.HitRegion_L_FootCrystalAqua:BehaviorProviderDefinition_0
• GD_Orchid_CrystaliskAqua.HitRegions.HitRegion_R_FootCrystalAqua:BehaviorProviderDefinition_0
• GD_Orchid_PirateQueen_Combat.Character.AIDef_Orchid_PirateQueen_Combat:AIBehaviorProviderDefinition_1
• GD_Sage_SM_BigFeetData.Creature.Character.AIDef_Sage_BigFeet_Creature:AIBehaviorProviderDefinition_1

Sourcecode

The code (and data) for this page exist at github: https://github.com/apocalyptech/borderlands-bpd. The code is licensed under the 3-clause BSD license. Feel free to run it locally yourself, if you like, or even host it elsewhere. I intend to keep hosting this on my own site, but should it ever go dark, having mirrors is always nice.

TODO

• Kismet Sequence objects should be able to autodetect what level they're in.
• Would be really nice to figure out a way to get graphs to scrunch down to be more square, rather than being so wide a lot of the time.
• Search/Highlight functionality
• Figure out other useful attributes to display in the nodes themselves, based on node type (mostly just for Kismets)
• Sort level names by DLC

Changelog