Initial commit

This commit is contained in:
2026-03-15 14:54:49 +03:00
commit 64f8029c06
4027 changed files with 254888 additions and 0 deletions

View File

@@ -0,0 +1,13 @@
root = true
[*]
end_of_line = lf
[*.{editorconfig,json,yml,lua,txt,md,sh}]
trim_trailing_whitespace = true
insert_final_newline = true
indent_style = space
indent_size = 4
charset = utf-8

View File

@@ -0,0 +1,87 @@
#
# Check the docs on how to write GitHub forms:
# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
#
name: "🪳 Bug Report"
description: Report a bug in DarkRP.
title: "<Title>"
body:
- type: markdown
attributes:
value: |
This place is only intended for bug reports.
If you need help, join the **[DarkRP Discord](https://darkrp.page.link/discord)**
- type: textarea
id: problem
validations:
required: true
attributes:
description: |
Describe the issue as accurately as possible.
placeholder: |
I'm unable to do x when ..
label: Problem
- type: textarea
id: reproduce
validations:
required: false
attributes:
description: |
Describe how we can reproduce the issue.
placeholder: |
1. I first do x
2. Then I do y and see z
label: Reproduction
- type: markdown
attributes:
value: |
It's important for us to be able to reproduce your problem
so we fix it more easily and be sure it's solved.
- type: textarea
id: errors
validations:
required: false
attributes:
description: |
Provide any errors. Please make sure to look at both the server
console as well as the console when you join the server.
placeholder: |
attempt to index 'foo' (a nil value)
some_file.lua: 123
label: Errors
- type: markdown
attributes:
value: |
Please always check the startup log of the server for
errors, as those can cause more errors down the line.
- type: textarea
id: extra
attributes:
description: |
Any additional information that you can provide.
label: Additional Info

View File

@@ -0,0 +1,9 @@
blank_issues_enabled: true
contact_links:
- about: Sadly, DarkRP is in maintenance only mode, meaning feature requests are generally not accepted. The best way to get the feature might be to create an addon.
name: 🆕 Feature request
url: https://darkrp.page.link/discord
- about: I need help with DarkRP
name: 🚨 Support
url: https://darkrp.page.link/discord

View File

@@ -0,0 +1,119 @@
#!/usr/bin/env bash
#
# Prints a list of errors for any dependencies that have been edited.
# Dependencies should be edited in their respective repositories
#
echo 'Checking for any dependency changes.'
set -o errexit # Exit for any error
set -o nounset # Error when referencing unset vars
commit=$(
git rev-list \
--first-parent origin/master \
--max-count=1
)
files=$(
git diff \
--name-only \
"$commit"
)
# Template for the GitHub summary
template="
> [!WARNING]
> Files from **[{project}]({repository})** have been modified!
> These changes originally come from [{project}]({repository}), but are synchronized to DarkRP.
> These files should be edited in the original repositories instead.
>
{files}
>
"
# Trim leading space for Markdown compatibility
template="$( echo "$template" | sed 's/^[[:space:]]*//' )"
failed=false
function check {
local name="$1"
local path="^$2"
local repo="$3"
# Check if any matching files were modified
local matched=$(
echo "$files" |
grep --perl-regexp "$path"
)
# Ignore if nothing matched
if [ -z "$matched" ] ; then
return
fi
# Append info to GitHub's summary
local info="$template"
matched="$(printf -- '> `%s` \n' "$matched")"
info=${info//\{repository\}/$repo}
info=${info//\{project\}/$name}
info=${info//\{files\}/$matched}
echo "$info" >> "$GITHUB_STEP_SUMMARY"
failed=true
}
check "Falco's Prop Protection" \
'gamemode/modules/fpp/pp/' \
'https://github.com/fptje/falcos-Prop-protection'
check "FN Library" \
'gamemode/libraries/fn.lua' \
'https://github.com/fptje/GModFunctional'
check "MySQLite Library" \
'gamemode/libraries/mysqlite/mysqlite.lua' \
'https://github.com/fptje/MySQLite'
check "Simplerr Library" \
'gamemode/libraries/simplerr.lua' \
'https://github.com/fptje/simplerr'
check "CAMI Library" \
'gamemode/libraries/sh_cami.lua' \
'https://github.com/glua/CAMI'
check "FSpectate" \
'gamemode/modules/fspectate/' \
'https://github.com/fptje/FSpectate'
if [[ "$failed" = true ]] ; then
echo 'Some dependencies have been modified!'
exit 1
fi
echo 'No dependencies have been modified.'
exit 0

View File

@@ -0,0 +1,20 @@
name: Check Modified Subtree
on:
workflow_dispatch:
pull_request:
branches: [master]
jobs:
check:
runs-on: ubuntu-latest
steps:
- name: Checkout Repository
uses: actions/checkout@v4
with:
fetch-depth: 0 # Fetch complete history
clean: false
- name: Check For Differences
run: ./.github/scripts/check-modified-subtree.sh

View File

@@ -0,0 +1,11 @@
name: run-glualint
on:
push:
branches:
- master
pull_request:
jobs:
Lint:
uses: FPtje/GLuaFixer/.github/workflows/glualint.yml@master
with:
config: "glualint.json"

View File

@@ -0,0 +1,78 @@
# THE GITHUB ISSUES PAGE IS NOT FOR GETTING HELP!
Remember that! We've got a Discord for that kind of stuff. It can be found here:
https://darkrp.page.link/discord
# What to do when you have a problem in DarkRP
There are three kinds of problems that can happen in DarkRP:
- The problem caused by the end user (think of a bad modification or a bad setting)
- The problem caused by a mod for DarkRP (think of a weapon pack, model pack or extra money printers or things like that)
- The problem for which the developer of DarkRP is responsible
The very first step of solving your problem is figuring out who caused it. Often this is easy to figure out. If DarkRP started to error
when you edited your HUD, it's probably your fault (or the server host's). If the server starts in sandbox, or if you get the error
```
"couldn't include file <ANYTHING> (File not found)"
```
it's your fault. Did you try uploading the entire unzipped DarkRP folder to the server with FileZilla? That's a known problem, it's FileZilla's fault. Half of your files didn't upload properly.
When a weapon from a weapon pack does crazy things, it's probably the person who made that weapon pack.
When the problem occurs with unedited DarkRP features, it might be DarkRP's fault.
There are cases for which it might be difficult to determine who is responsible for the problem.
In these cases you should look at the errors that usually show up. The errors usually say which mod caused the problem.
If it's your fault, blame yourself. If you caused a problem you don't know how to solve, you have two options:
<ol>
<li>ask on a forum or ask your friends for help. If you contact mod developers, they might get mad at you for being asked something they have nothing to do with</li>
<li>undo the change that broke DarkRP. To do this, always make sure you have a backup</li>
</ol>
If it's the fault of a third party mod developer, contact them to report the bug. They are the only ones who can (and are willing to)
solve the problems caused by their mod.
# Reporting a bug for DarkRP
Only report bugs for issues of which you are VERY SURE that it is the fault of DarkRP developers.
To report a bug for DarkRP, you need to follow very strict rules. These rules exist so the bugs can be easily identified and solved.
The most important rules are:
<ol>
<li>Do not ask for help. Your need of help is not the fault of DarkRP.</li>
<li>Do not report an issue when you are unable to install DarkRP.</li>
<li>Do not report problems that you caused yourself.</li>
<li>Do not report problems for other mods.</li>
<li>Do not report problems for a server that you do not own or develop for</li>
<li>Do not report a problem that has been reported before (you can search on the bug reporting site)</li>
<li>Do not repost your problem when your previous problem has been closed. You can post in a closed issue and you will still be listened to.</li>
<li>Never just post "It doesn't work" that's no information to work on.</li>
</ol>
Failure to abide by these rules will get your report closed and/or your account banned from reporting issues.
How to report a bug:
<ol>
<li> Enter lua_log_sv 1 in RCon or the server console</li>
<li> Make the problem happen</li>
if a weapon messes up when you shoot, shoot the weapon.
if it happens on server start, change level or restart the server
if it happens when the mayor tries to place a lawboard, make the mayor try to spawn a lawboard
etc.</li>
<li> Go to the FTP of your server.</li>
<li> In the garrysmod/ folder you should see "lua_errors_server.txt" and/or "clientside_errors.txt"
upload the contents of BOTH these files to www.pastebin.com
if you don't see those files, make sure you did everything right (lua_log_sv must be 1).
if you don't see the files and you're sure that you did the logging right, mention this in the bug report:
"No error log files were generated."
If you only see one file, upload that one file to www.pastebin.com and mention the following in the bug report:
"The other error log file was not generated."
Thanks. Errors help A LOT.</li>
<li> Go to https://github.com/FPtje/DarkRP/issues/new (DON'T SKIP THE PREVIOUS STEPS)</li>
<li> Think of an appropriate title. Try to be specific here</li>
<li> Take the issue template from "github issue template.txt", which is in the HELP folder, and copy paste it into the "Write" field.</li>
<li> Fill it in, try not to leave anything empty!</li>
MORE information = MUCH HIGHER chance that the problem will be solved
<li> Click "Submit new issue"</li>
</ol>

View File

@@ -0,0 +1,35 @@
DO NOT EDIT ANY FILES OF THE DARKRP GAMEMODE. THAT IS SIMPLY NOT HOW YOU MODIFY DARKRP
Do not modify ANY files, not in the modules, not in the config folder, not ANYWHERE in this folder.
Here's what happens if you fuck with DarkRP files:
- You won't be able to update anymore. And yes you do care about updates because they have new features and bug fixes.
Problems often get solved in updates, that is if you didn't fuck it up yourself.
- ANY problem you have with DarkRP will NOT be any of the developer's responsibility.
YOU fucked with the DarkRP files, and now it's broken. Therefore it is your fault by default.
You were warned. All support is immediately dropped when you edit DarkRP files
- When GMod updates, shit will break and you won't know what the fuck to do.
You won't know how to fix it
and you can't update DarkRP to the working version because you fucked it up.
Wanting to edit DarkRP files doesn't make you batshit insane unless you think the following:
"I'll modify DarkRP, but when there's an update, I'll MANUALLY COPY THE CHANGED FILES OVER."
This is retarded. Actually proper retarded. This is the absolute dumbest thing you can possibly do.
What if you're reluctant to update for just a week and find out pretty much every file was changed? Yes, this happens.
You'd have to copy the changes over one by fucking one. Are you going to do that?
No you fucking won't. It will take fucking hours of tedious and unnecessary work. You'll say "Bollocks, fuck it".
And your DarkRP is never to be updated properly again.
================================== IMPORTANT ==================================
THERE IS ANOTHER WAY TO MODIFY DARKRP WITHOUT HAVING TO FUCK WITH THE DARKRP FOLDER
IT'S JUST AS EASY
AND YOU CAN STILL UPDATE DARKRP
================================== IMPORTANT ==================================
Of course you can modify DarkRP, I'd be daft if I forbade you. Just don't do it by editing DarkRP files.
Get the DarkRP modification addon.
https://github.com/FPtje/DarkRPModification
You will be surprised about how much you do with it.

View File

@@ -0,0 +1,35 @@
Avoid editing DarkRP core files AT ALL COST!
DarkRP files are not meant for you to be edited, not even the config folder.
Anything in DarkRP should be changeable without having to change core DarkRP files.
If this isn't possible, it should be MADE possible.
Open an issue on GitHub if there is no
- DarkRP function that allows you to change DarkRP the way you want:
https://darkrp.miraheze.org/wiki/Category:Functions
- DarkRP Hook that allows you to change DarkRP the way you want:
https://darkrp.miraheze.org/wiki/Category:Hooks
--[[---------------------------------------------------------------------------
How to configure
---------------------------------------------------------------------------]]
Download https://github.com/FPtje/DarkRPModification as an addon and use the
config folder inside it to configure DarkRP.
--[[---------------------------------------------------------------------------
How to modify DarkRP without modifying the core files
---------------------------------------------------------------------------]]
1. Go to darkrpmodification/lua/darkrp_modules
2. Make a folder with any name, e.g. mydarkrpmod
it has to be lowercase
no spaces or weird characters
3. go into mydarkrpmod
4. if you're doing a serverside thing, make a Lua file that starts with sv_
e.g. sv_init.lua
if you're doing a clientside thing, make a Lua file that starts with cl_
e.g. cl_init.lua
if you're doing a shared thing, make a Lua file that starts with sh_
e.g. sh_init.lua
if you don't know what serverside/clientside/shared is, you should probably not be trying to modify DarkRP.
5. Use the DarkRP functions and hooks (and other functions/hooks) to make your thing

View File

@@ -0,0 +1,4 @@
The official DarkRP wiki can be found at
https://darkrp.miraheze.org/wiki/Main_Page
You can find out how to make custom jobs, shipments and many other things there!

View File

@@ -0,0 +1,5 @@
Put the darkrp folder in garrysmod/gamemodes
IF YOU PUT DARKRP IN ADDONS IT WON'T WORK!
REMOVE OLD DARKRP FOLDER BEFORE PUTTING THE NEW ONE IN

View File

@@ -0,0 +1,70 @@
--[[---------------------------------------------------------------------------
What to do when you have a problem in DarkRP
---------------------------------------------------------------------------]]
There are three kinds of problems that can happen in DarkRP:
- The problem caused by the end user (think of a bad modification or a bad setting)
- The problem caused by a mod for DarkRP (think of a weapon pack, model pack or extra money printers or things like that)
- The problem caused by the developer of DarkRP
The very first step of solving your problem is figuring out who caused it. Often this is easy to figure out. If DarkRP started to error
when you edited your HUD, it's probably your fault (or the server host's). If the server starts in sandbox, or if you get the error
"couldn't include file darkrp\gamemode\cl_init.lua (File not found)"
it's your fault.
When a weapon from a weapon pack does crazy things, it's probably the person who made that weapon pack.
When the problem occurs with unedited DarkRP features, it might be DarkRP's fault.
There are cases for which it might be difficult to determine who is responsible for the problem.
In these cases you should look at the errors that usually show up. The errors usually say which mod caused the problem.
If it's your fault, blame yourself. If you caused a problem you don't know how to solve, you have two options:
1. ask on a forum or ask your friends for help. If you contact mod developers,
they might get mad at you for being asked something they have nothing to do with
2. undo the change that broke DarkRP. To do this, always make sure you have a backup
If it's the fault of a third party mod developer, contact them to report the bug. They are the only ones who can (and are willing to)
solve the problems caused by their mod.
--[[---------------------------------------------------------------------------
Reporting a bug for DarkRP
---------------------------------------------------------------------------]]
Only report bugs for issues of which you are VERY SURE that it is the fault of DarkRP developers.
To report a bug for DarkRP, you need to follow very strict rules. These rules exist so the bugs can be easily identified and solved.
The most important rules are:
1. Do not ask for help. Your need of help is not the fault of DarkRP.
2. Do not report an issue when you are unable to install DarkRP.
3. Do not report problems that you caused yourself.
4. Do not report problems for other mods.
5. Do not report problems for a server that you do not own or develop for
6. Do not report a problem that has been reported before (you can search on the bug reporting site)
7. Do not repost your problem when your previous problem has been closed. You can post in a closed issue and you will still be listened to.
8. Never just post "It doesn't work" that's no information to work on.
Failure to abide by these rules will get your report closed and/or your account banned from reporting issues.
How to report a bug:
1. Enter lua_log_sv 1 in RCon or the server console
2. Make the problem happen
if a weapon messes up when you shoot, shoot the weapon.
if it happens on server start, change level or restart the server
if it happens when the mayor tries to place a lawboard, make the mayor try to spawn a lawboard
etc.
3. Go to the FTP of your server.
4. In the garrysmod/ folder you should see "lua_errors_server.txt" and/or "clientside_errors.txt"
upload the contents of BOTH these files to www.pastebin.com
if you don't see those files, make sure you did everything right (lua_log_sv must be 1).
if you don't see the files and you're sure that you did the logging right, mention this in the bug report:
"No error log files were generated."
If you only see one file, upload that one file to www.pastebin.com and mention the following in the bug report:
"The other error log file was not generated."
Thanks. Errors help A LOT.
5. Go to https://github.com/FPtje/DarkRP/issues/new (DON'T SKIP THE PREVIOUS STEPS)
6. Think of an appropriate title. Try to be specific here
7. Take the issue template from "github issue template.txt" and copy paste it into the "Write" field.
8. Fill it in, try not to leave anything empty!
MORE information = MUCH HIGHER chance that the problem will be solved
9. Click "Submit new issue"

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,21 @@
The MIT License (MIT)
Copyright (c) 2014 Falco Peijnenburg
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

View File

@@ -0,0 +1,31 @@
# DarkRP ![run-glualint](https://github.com/FPtje/DarkRP/workflows/run-glualint/badge.svg?branch=master)
A roleplay gamemode for Garry's Mod.
## Getting DarkRP
Please use either git or the workshop.
Manually downloading DarkRP or using SVN is possible, but not recommended.
The workshop version of DarkRP can be found here:
https://steamcommunity.com/sharedfiles/filedetails/?id=248302805
## Modifying DarkRP
Check out the wiki!
https://darkrp.miraheze.org/wiki/Main_Page
Make sure to download the DarkRPMod:
https://github.com/FPtje/darkrpmodification
Do you want to create a gamemode based on DarkRP?
You probably shouldn't. If you insist, use the derived gamemode that can be downloaded here:
https://github.com/FPtje/DarkRP/releases/tag/derived
Just whatever you do, don't touch DarkRP's core files.
## Getting help
Please head to the official Discord!
https://darkrp.page.link/discord

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/back"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

Binary file not shown.

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/access"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/ban"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/changeteam"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/chatmute"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/cleanup"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/cloak"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/disable"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/freeze"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/god"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/ignite"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/jail"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/kick"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/message"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/motd"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/noclip"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/pickup"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/ragdoll"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/rcon"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/serversetting"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/slap"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/slay"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/spectate"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/teleport"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/voicemute"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,8 @@
"UnlitGeneric"
{
"$basetexture" "fadmin/icons/weapon"
"$ignorez" 1
"$vertexcolor" 1
"$vertexalpha" 1
"$nolod" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/arrest_stick"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/door_ram"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/keys"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/lockpick"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/ls_sniper"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/med_kit"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/pocket"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/stunstick"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/unarrest_stick"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_ak472"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_deagle2"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_fiveseven2"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_glock2"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_keypadchecker"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_m42"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

View File

@@ -0,0 +1,7 @@
"UnlitGeneric"
{
"$basetexture" "VGUI/entities/weapon_mac102"
"$vertexcolor" 1
"$vertexalpha" 1
"$translucent" 1
}

Some files were not shown because too many files have changed in this diff Show More