A few things you need to know:
- There is no more toybox, instead we now have the steam workshop. If you want to download ALL of the toybox content, go here
- Legacy addons need their info.txt renamed to addon.txt otherwise they will NOT be detected and mounted by gmod.
Why your shit broke:
Garry replaced and refactored a lot of shit during the beta. This includes replacing functions, getting rid of some, and renaming others, meaning, that unless you were REALLY lucky,
almost all of your addons will break. But trust us, this is FOR THE BETTER! These kinds of changes make gmod quite a bit more efficient, stable, and easier to code for!
How to Fix it:
Firstly, if the addon you are using is popular/well maintained (i.e. wiremod) chances are the author already updated it to gmod13, so all you have to do is
A) wait for an update from them and re-download or
B) wait for it to be put on the steam workshop and get it from there.
If however, you are either less patient or your addon is no longer maintained, 95% of errors are easy find/replace fixes. Here is what you do:
1) When in game, you will get an error from your addon (note: these no longer print on your screen instead they go directly to the console) and it will look something like this:
[ERROR] gamemodes/terrortown/gamemode/weaponry.lua:158: attempt to call method 'IsSpec' (a nil value) 1. Call - gamemodes/terrortown/gamemode/weaponry.lua:158 2. unknown - gamemodes/base/gamemode/player.lua:248
Obviously yours won’t look exactly like this, but the general information would be the same.
Here’s how the errors break down:
The first line tells you it’s an error, and then prints the file and the line in the file where the error happened.
That information is then followed by a description of the error. Most of the time, your errors will be “attempt to call method ‘SOME_NAME_HERE’ (a nil value)”
meaning that gmod couldn’t find the exact function name.
The numbered lines are called a “stack trace”. You probably won’t need to worry about them, unless the file the first line talks about doesn’t exist (aka it’s garrys file)
then you need to go to the files shown on the “stack trace” to figure out what’s wrong.
2) Once you have found the place where the error is happening and the thing that gmod can’t find, go here
This is a complete change list of what was done in the beta. At this point, all you have to do is use ctrl+f
to find the thing gmod tells you it couldn’t in this file. Let me give an example:
Say that gmod told me it couldn't find "ValidEntity", so I would search the document for it and get the following line: "Removed ValidEntity( ent ) (replace with IsValid( ent ))" So the thing I want to copy now is "IsValid"
3) Finally, now that you have the new name for the function (or whatever) go back to your file and user ctlr+h to replace all copies of the bad code with the new one you found in the document.
So I would replace all occurances of "ValidEntity" with "IsValid"
- Figure out what fucked up.
- Go here to figure out what to replace it with.
- Replace all occurrences of bad code with the new stuff fromt the above link.
Please note: The above guide is EXTREMELY BASIC, but it should help you fix 95% of problems that arise. HOWEVER, there are issues that are a tad more complex and will need more than basic knowledge of lua, such as the arguments for functions changing. If you find yourself in a situation like that (AFTER using this guide!) feel free to post to the “What do you need help with” thread, and we will try to help you out.
If you guys find a mistake, let me know and I’ll fix it.