User Tools

Site Tools


contents

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
contents [2025/05/26 06:49] – created some_random_idiotcontents [2025/05/26 08:01] (current) some_random_idiot
Line 3: Line 3:
  
 ---- ----
 +<WRAP center round important 70%>
 +Allow all custom files in your game settings before debugging or reporting missing contents as a bug!
 +</WRAP>
 +
 ===== WorkshopDL ===== ===== WorkshopDL =====
 <WRAP round box> <WRAP round box>
Line 8: Line 12:
  
 <WRAP round info> <WRAP round info>
 +This method's progress can be seen in the "Downloading workshop addons..." dialogue box while joining.
 +
 The following Steam Workshop collection is used to carry out this process along with some serverside scripts: [[https://steamcommunity.com/workshop/filedetails/?id=2459565773]] The following Steam Workshop collection is used to carry out this process along with some serverside scripts: [[https://steamcommunity.com/workshop/filedetails/?id=2459565773]]
 </WRAP> </WRAP>
Line 14: Line 20:
 ===== Hotloading ===== ===== Hotloading =====
 <WRAP round box> <WRAP round box>
-While not an official term, hotloading is a very effective way of fetching sounds and models lazily. This is done by asynchronously downloading addons from the workshop and then slowly mounting them to mitigate crashes. This, being a non-sequential process, allows the player to join the server without having to wait for the files to be fully downloaded first. **The tradeoff of this method is that they may see missing textures and errors for a bit depending on their setup.** This method can be seen doing its thing when a workshop popup that has the word "Hotload" appears. Although, subsequent joins will see it using local files instead, which are shown as numbers.+While not an official method, hotloading is a very effective way of fetching sounds and models lazily. This is done by asynchronously downloading addons from the workshop and then slowly mounting them to mitigate crashes. This, being a non-sequential process, allows the player to join the server without having to wait for the files to be fully downloaded first. **The tradeoff of this method is that they may see missing textures and errors briefly.**  
 + 
 +<WRAP round info> 
 +This method can be seen doing its thing when a workshop download popup with the word "Hotload" appears while joining or in the game. Although, subsequent joins will see it using local files instead, which are shown as numbers in the popup. 
 + 
 +When the downloads are finished, it will begin mounting the downloaded contents, which can be heard as "tu-tae-tu" sounds in regular intervals. 
 +</WRAP>
 </WRAP> </WRAP>
  
Line 32: Line 44:
 ===== gluapack ===== ===== gluapack =====
 <WRAP round box> <WRAP round box>
-Basically [[https://wiki.facepunch.com/gmod/Serving_Content#fastdl|FastDL]] for scripts, gluapack packs <wrap lo>(heh)</wrap> the server's Lua files into a map file and then upload it to its dedicated web server so that players can download it from there. This method is prefered because traditional Lua file sending is mind-numbingly limited speed wise. The only catch with this method is that the player has to atleast allow map file downloading. If you don't have that enabled I don't know what to tell you.+Basically [[https://wiki.facepunch.com/gmod/Serving_Content#fastdl|FastDL]] for scripts, gluapack packs <wrap lo>(heh)</wrap> the server's Lua files into a map file and then upload it to its dedicated web server so that players can download it from there. This method is prefered because traditional Lua file sending is mind-numbingly limited speed wise. **The only catch with this method is that the player has to atleast allow map file downloading, and that there are cases where it fails for some players.**
 </WRAP> </WRAP>
contents.1748242145.txt.gz · Last modified: by some_random_idiot