Note: this is an old tutorial. The information may still be useful, you will probably be better served by the new one, Tutorial: Getting Started Making Mods.
BE FOREWARNED: HERE BE SMALL DRAGONS
It is best to understand how to use normal set commands first before diving into hotfixes. See Here
All things Borderlands 2. Borderlands 2 VR. Borderlands 2 VR Update / Hot-Fix Information; Submitting a Support Ticket for Borderlands 2 VR.
![]()
(original version of this page thanks to adudney)
Hotfixes behave exactly like set commands but delay taking effect until you enter the game. This allows for changing things such as skills and enemies, which only load once you're actually in game.
In general, if you can
obj dump something from the console at the main menu, you can use a regular set command, but if you can't, then you'll have to use a Hotfix instead.
There are 3 types of hotfix: Patch, On Demand, and Level.
BLCMM makes it very easy to create a hotfix: just click the 'Hotfix' checkbox at the top of the code edit window. You can use the dropdown to choose whether to create a Patch, On Demand, or Level hotfix, choose the level name or package name, and optionally give the hotfix a descriptive name. Bernette 203 manual download. The code you write continues to look just like a regular
set command that you're already familiar with.
In addition to giving you access to objects which aren't loaded by default otherwise, and providing level-and-character specific commands, hotfixes also let us do a few other things that we can't do with ordinary
set statements.
Targetted EditsManual Download Bl2 Hotfixes 1
One is that we can 'drill into' a data structure. For instance, if you wanted to change Gettle's drop from the Lyuda to the Pitchfork with a regular
set statement, which you'd do in GD_Itempools.Runnables.Pool_Gettle , you'd have to set the entireBalancedItems structure, with a statement that looks something like:
Whereas if you used a hotfix, you'd be able to do a statement like this:
Manual Download Bl2 Hotfixes For Mac
Much more concise!
Comparison Edits
The other thing that hotfixes can do is set themselves to only execute if the attribute being changed is already equal to a known value. This is basically never used in community-created mods, but Gearbox uses this in some of their official hotfixes, and there's nothing preventing mod authors from doing it as well. For instance, one of the default Gearbox hotfixes in BL2 is:
So that particular phase of Varkid evolution will be changed to
0.8 , but only if it was 0.7 to begin with. If some other statement has already changed the evolution change before that hotfix has a chance to execute, the hotfix won't actually do anything.
Adding to Arrays (TPS only)
The Pre-Sequel added an interesting feature to hotfixes where you can add to an existing array without having to redefine the whole thing. For instance, one of the default Gearbox TPS hotfixes looks like this (edited a bit for length):
Which adds the pool
GD_Itempools.Runnables.Pool_ScavBadassSpacemanMidget to Swagman's drop pool. Unfortunately, this syntax is not available in BL2.
FilterTool already abstracted hotfixes so that you don't need to know what they actually look like in the file, and BLCMM takes it further. When constructing hotfixes in BLCMM, you just write
set statements like you're used to doing, just with an extra checkbox selected at the top of the window. So, keep in mind that you should never have to actually know any of the information in this section.
Manual Download Bl2 Hotfixes 2
If you ever do look into the actual files themselves, though, hotfixes are structured as such:
Note that
level , package , and old_value can be empty.
Additionally, each hotfix has a name associated with it. If you look at the bottom of a patch file with hotfixes, you'll see two set statements:
So the names go into
Keys and the hotfixes themselves go into Values .
Manual Download Bl2 Hotfixes FreeComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |