We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Title of the Bug Armoury Lockpick Purchase Error
Description When buying an Armoury Lockpick from the shop NPC, you will be met with an error message (you still receive the lockpick)
Steps to Reproduce (Your goto way to recreate this bug.)
Expected Behavior Should not receive an error message
Actual Behavior Players will be met with an error when purchasing the lockpick
Evidence (If possible, please put any screenshots or videos)
[police_armory_locker] addons/police_armory_locker/lua/weapons/armory_lockpick/shared.lua:61: bad argument #1 to 'SetDeploySpeed' (number expected, got nil)
The text was updated successfully, but these errors were encountered:
https://steamcommunity.com/sharedfiles/filedetails/?id=1917043256 added to the resource file. Also fixed SetDeploySpeed error in Lua. This value doesn't seem to exist in the addon. Might be worth seeing if the latest version of the addon has any other fixes.
Sorry, something went wrong.
relz999
No branches or pull requests
Title of the Bug
Armoury Lockpick Purchase Error
Description
When buying an Armoury Lockpick from the shop NPC, you will be met with an error message (you still receive the lockpick)
Steps to Reproduce
(Your goto way to recreate this bug.)
Expected Behavior
Should not receive an error message
Actual Behavior
Players will be met with an error when purchasing the lockpick
Evidence
(If possible, please put any screenshots or videos)
[police_armory_locker] addons/police_armory_locker/lua/weapons/armory_lockpick/shared.lua:61: bad argument #1 to 'SetDeploySpeed' (number expected, got nil)
The text was updated successfully, but these errors were encountered: