Upvote Upvoted 0 Downvote Downvoted
Custom folder
posted in Customization
1
#1
0 Frags +

.

.
2
#2
2 Frags +

it's more likely that you're in the wrong folder than there being something wrong with your game

it's more likely that you're in the wrong folder than there being something wrong with your game
3
#3
-4 Frags +

.

.
4
#4
4 Frags +

#1
The answer to your question would be yes.

#1
The answer to your question would be yes.
5
#5
1 Frags +

.

.
6
#6
1 Frags +

Give us the path man

Give us the path man
7
#7
0 Frags +

make a folder in the custom folder and name it "stuff" or whatever you prefer and put all that shit in there

make a folder in the custom folder and name it "stuff" or whatever you prefer and put all that shit in there
8
#8
0 Frags +

.

.
9
#9
1 Frags +
readme.txtWhen the game boots, this folder [..\tf\custom] is automatically scanned for VPK files or
subfolders. Each subfolder or VPK is added as a search path, so the files
inside those VPK's or subfolders will override the default game files.

See gameinfo.txt for more details.

For example, you might have the following file structure:

tf/custom/my_custom_stuff/ <<< This subfolder will be added as a search path
tf/custom/my_custom_stuff/models/custom_model.mdl
tf/custom/my_custom_stuff/materials/custom_material.vmt
tf/custom/my_custom_stuff/materials/vgui/custom_ui_thing.res
tf/custom/some_mod.vpk <<< This VPK will be added as a search path
tf/custom/another_mod.vpk <<< This VPK will be added as a search path

Mounting a VPK to the filesystem is more efficient than adding a subfolder,
as each time the engine needs to open a file, it will need to make a call to the
operating system to search the folder. VPKs can therefore be searched by the engine
much more efficiently. Each subfolder is a new search path that must be checked each
time the engine tries to open a file. So, for optimal load times, always use VPK files
and don't make any subfolders in this folder!

Note that the following directory structure is NOT correct:

tf/custom/models/my_model.mdl

That will add the directory "tf/custom/models" as a search path, in which case the
file my_model.mdl actually exists at the root of the game's virtual filesystem.
Instead, you would use something like:

tf/custom/my_custom_stuff/models/my_model.mdl

Note that some huds don't work properly from VPKs, for reasons I have not bothered to investigate.

[quote=readme.txt]When the game boots, this folder [..\tf\custom] is automatically scanned for VPK files or
subfolders. Each subfolder or VPK is added as a search path, so the files
inside those VPK's or subfolders will override the default game files.

See gameinfo.txt for more details.

For example, you might have the following file structure:

tf/custom/my_custom_stuff/ <<< This subfolder will be added as a search path
tf/custom/my_custom_stuff/models/custom_model.mdl
tf/custom/my_custom_stuff/materials/custom_material.vmt
tf/custom/my_custom_stuff/materials/vgui/custom_ui_thing.res
tf/custom/some_mod.vpk <<< This VPK will be added as a search path
tf/custom/another_mod.vpk <<< This VPK will be added as a search path


Mounting a VPK to the filesystem is more efficient than adding a subfolder,
as each time the engine needs to open a file, it will need to make a call to the
operating system to search the folder. VPKs can therefore be searched by the engine
much more efficiently. Each subfolder is a new search path that must be checked each
time the engine tries to open a file. So, for optimal load times, always use VPK files
and don't make any subfolders in this folder!


Note that the following directory structure is NOT correct:

tf/custom/models/my_model.mdl

That will add the directory "tf/custom/models" as a search path, in which case the
file my_model.mdl actually exists at the root of the game's virtual filesystem.
Instead, you would use something like:

tf/custom/my_custom_stuff/models/my_model.mdl
[/quote]

Note that some huds don't work properly from VPKs, for reasons I have not bothered to investigate.
10
#10
0 Frags +

.

.
11
#11
-2 Frags +

.

.
12
#12
3 Frags +

folders should be like this:

Custom > My_custom_stuff > cfg > All your configs (such as maxframes and class files.)

Hud files should be in the Custom folder not my_custom_stuff along with prec
Sound folder for a new histound should be in my_custom_stuff

Or use this https://www.youtube.com/watch?v=FO5oEk13tKY

folders should be like this:

Custom > My_custom_stuff > cfg > All your configs (such as maxframes and class files.)

Hud files should be in the Custom folder not my_custom_stuff along with prec
Sound folder for a new histound should be in my_custom_stuff


Or use this https://www.youtube.com/watch?v=FO5oEk13tKY
13
#13
-1 Frags +

.

.
14
#14
0 Frags +
epireadme.txtWhen the game boots, this folder [..\tf\custom] is automatically scanned for VPK files or
subfolders. Each subfolder or VPK is added as a search path, so the files
inside those VPK's or subfolders will override the default game files.

See gameinfo.txt for more details.

For example, you might have the following file structure:

tf/custom/my_custom_stuff/ <<< This subfolder will be added as a search path
tf/custom/my_custom_stuff/models/custom_model.mdl
tf/custom/my_custom_stuff/materials/custom_material.vmt
tf/custom/my_custom_stuff/materials/vgui/custom_ui_thing.res
tf/custom/some_mod.vpk <<< This VPK will be added as a search path
tf/custom/another_mod.vpk <<< This VPK will be added as a search path

Mounting a VPK to the filesystem is more efficient than adding a subfolder,
as each time the engine needs to open a file, it will need to make a call to the
operating system to search the folder. VPKs can therefore be searched by the engine
much more efficiently. Each subfolder is a new search path that must be checked each
time the engine tries to open a file. So, for optimal load times, always use VPK files
and don't make any subfolders in this folder!

Note that the following directory structure is NOT correct:

tf/custom/models/my_model.mdl

That will add the directory "tf/custom/models" as a search path, in which case the
file my_model.mdl actually exists at the root of the game's virtual filesystem.
Instead, you would use something like:

tf/custom/my_custom_stuff/models/my_model.mdl

Note that some huds don't work properly from VPKs, for reasons I have not bothered to investigate.

HUDs do work, the fonts don't work from VPKs

[quote=epi][quote=readme.txt]When the game boots, this folder [..\tf\custom] is automatically scanned for VPK files or
subfolders. Each subfolder or VPK is added as a search path, so the files
inside those VPK's or subfolders will override the default game files.

See gameinfo.txt for more details.

For example, you might have the following file structure:

tf/custom/my_custom_stuff/ <<< This subfolder will be added as a search path
tf/custom/my_custom_stuff/models/custom_model.mdl
tf/custom/my_custom_stuff/materials/custom_material.vmt
tf/custom/my_custom_stuff/materials/vgui/custom_ui_thing.res
tf/custom/some_mod.vpk <<< This VPK will be added as a search path
tf/custom/another_mod.vpk <<< This VPK will be added as a search path


Mounting a VPK to the filesystem is more efficient than adding a subfolder,
as each time the engine needs to open a file, it will need to make a call to the
operating system to search the folder. VPKs can therefore be searched by the engine
much more efficiently. Each subfolder is a new search path that must be checked each
time the engine tries to open a file. So, for optimal load times, always use VPK files
and don't make any subfolders in this folder!


Note that the following directory structure is NOT correct:

tf/custom/models/my_model.mdl

That will add the directory "tf/custom/models" as a search path, in which case the
file my_model.mdl actually exists at the root of the game's virtual filesystem.
Instead, you would use something like:

tf/custom/my_custom_stuff/models/my_model.mdl
[/quote]

Note that some huds don't work properly from VPKs, for reasons I have not bothered to investigate.[/quote]

HUDs do work, the fonts don't work from VPKs
15
#15
1 Frags +

.

.
16
#16
2 Frags +

Take the folders out of the hudasiscariote directory and place them in Hudas Iscariote [Version 1.5.1] instead. Though you should probably just have a "my_custom_stuff" or whatever you wanna name the folder as a general sub-directory for uh. custom stuff instead. But this is not necessary.

What the game does, put simply, is check for sub-directories within the "custom" folder, and then applies the appropriately named directories within THAT to the game. So if you have a "materials" folder in "my_custom_stuff", or in your case "Hudas Iscariote [Version 1.5.1]", the folder and files in there will overwrite the game's regular "materials" files, if that makes sense. It won't work if you hide the replacement folders (materials, sound, scripts, resource, etc) inside more sub-directories.

Also vpks are basically sub-directories themselves, hence why they go directly into the custom folder.

Take the folders out of the hudasiscariote directory and place them in Hudas Iscariote [Version 1.5.1] instead. Though you should probably just have a "my_custom_stuff" or whatever you wanna name the folder as a general sub-directory for uh. custom stuff instead. But this is not necessary.

What the game does, put simply, is check for sub-directories within the "custom" folder, and then applies the appropriately named directories within THAT to the game. So if you have a "materials" folder in "my_custom_stuff", or in your case "Hudas Iscariote [Version 1.5.1]", the folder and files in there will overwrite the game's regular "materials" files, if that makes sense. It won't work if you hide the replacement folders (materials, sound, scripts, resource, etc) inside more sub-directories.

Also vpks are basically sub-directories themselves, hence why they go directly into the custom folder.
17
#17
-5 Frags +

.

.
18
#18
2 Frags +

You're welcome Sackbutt01!

You're welcome Sackbutt01!
19
#19
-8 Frags +

hey i accidentaly deleted my readme.txt file -_- can anyone say what reads in the txt file cus as i said, i accidently deleted it cus im a retard! thx!

hey i accidentaly deleted my readme.txt file -_- can anyone say what reads in the txt file cus as i said, i accidently deleted it cus im a retard! thx!
20
#20
1 Frags +
When the game boots, this folder is automatically scanned for VPK files or
subfolders. Each subfolder or VPK is added as a search path, so the files
inside those VPK's or subfolders will override the default game files.

See gameinfo.txt for more details.

For example, you might have the following file structure:

tf/custom/my_custom_stuff/ <<< This subfolder will be added as a search path
tf/custom/my_custom_stuff/models/custom_model.mdl
tf/custom/my_custom_stuff/materials/custom_material.vmt
tf/custom/my_custom_stuff/materials/vgui/custom_ui_thing.res
tf/custom/some_mod.vpk <<< This VPK will be added as a search path
tf/custom/another_mod.vpk <<< This VPK will be added as a search path

Mounting a VPK to the filesystem is more efficient than adding a subfolder,
as each time the engine needs to open a file, it will need to make a call to the
operating system to search the folder. VPKs can therefore be searched by the engine
much more efficiently. Each subfolder is a new search path that must be checked each
time the engine tries to open a file. So, for optimal load times, always use VPK files
and don't make any subfolders in this folder!

Note that the following directory structure is NOT correct:

tf/custom/models/my_model.mdl

That will add the directory "tf/custom/models" as a search path, in which case the
file my_model.mdl actually exists at the root of the game's virtual filesystem.
Instead, you would use something like:

tf/custom/my_custom_stuff/models/my_model.mdl
[quote]When the game boots, this folder is automatically scanned for VPK files or
subfolders. Each subfolder or VPK is added as a search path, so the files
inside those VPK's or subfolders will override the default game files.

See gameinfo.txt for more details.

For example, you might have the following file structure:

tf/custom/my_custom_stuff/ <<< This subfolder will be added as a search path
tf/custom/my_custom_stuff/models/custom_model.mdl
tf/custom/my_custom_stuff/materials/custom_material.vmt
tf/custom/my_custom_stuff/materials/vgui/custom_ui_thing.res
tf/custom/some_mod.vpk <<< This VPK will be added as a search path
tf/custom/another_mod.vpk <<< This VPK will be added as a search path


Mounting a VPK to the filesystem is more efficient than adding a subfolder,
as each time the engine needs to open a file, it will need to make a call to the
operating system to search the folder. VPKs can therefore be searched by the engine
much more efficiently. Each subfolder is a new search path that must be checked each
time the engine tries to open a file. So, for optimal load times, always use VPK files
and don't make any subfolders in this folder!


Note that the following directory structure is NOT correct:

tf/custom/models/my_model.mdl

That will add the directory "tf/custom/models" as a search path, in which case the
file my_model.mdl actually exists at the root of the game's virtual filesystem.
Instead, you would use something like:

tf/custom/my_custom_stuff/models/my_model.mdl
[/quote]
21
#21
3 Frags +

What is this necro bullshit?
This isn't even the right thread for this.

What is this necro bullshit?
This isn't even the right thread for this.
22
#22
3 Frags +
Nilaghey i accidentaly deleted my readme.txt file -_- can anyone say what reads in the txt file cus as i said, i accidently deleted it cus im a retard! thx!

Tfw you post a comment in a year old thread that doesn't even relate to it

[quote=Nilag]hey i accidentaly deleted my readme.txt file -_- can anyone say what reads in the txt file cus as i said, i accidently deleted it cus im a retard! thx![/quote]

Tfw you post a comment in a year old thread that doesn't even relate to it
Please sign in through STEAM to post a comment.