Technical FAQ

[M!NT]

Why do I keep crashing?

Sadly crashes have become more and more common. We are actively working on it, but for now, here are some home things you can try:

1. Crash to Desktop (CTD):
   1. Make sure you meet the minimum technical specifications
   2. Disable multicore rendering
   3. Ensure that you have all of the content installed AND mounted (ep1, ep2, csgo, css)
   4. Verify your local gmod game files.
2. Timeout: This is (usually) because of packet loss problems:
   1. Connect to your router via ethernet for a more stable connection.
   2. Test your download/upload speeds to see if they are above the required 50mb/s down 5mb/s up.
   3. If you have a broadband copper connection, sometimes things like weather can affect packet loss.
   4. Try using a VPN.
3. Buffer overflow: Typically there is not a lot you can do at the moment if you meet the required specs. A buffer overflow in the realm of GMod happens because there is too much network traffic sitting in a box, and the code which consumes that traffic cannot run fast enough to take it out of the box. This typically happens when there is too much going on at one particular moment in time (especially when you're first loading in). If you are stuck in a buffer overflow loop when trying to join, please try the following:
   1. Unsubscribe from all your addons, open the game, and resubscribe to the WN content pack.
   2. Verify your local game files
   3. In your local gmod folders, clear out the contents of the 'data' and 'cache' folders
   4. Restart your computer

Generally speaking, lowering your graphics settings/resolution, making sure GMod is installed on an SSD, and being connected via Ethernet are the three things everyone should do if they can.

General Questions

Why is my ping so high?
The Willard Networks server is hosted in Germany. This is because most of our players are in the UK/EU so it serves them well. If you are currently in America (especially pacific), Eastern Europe, Australia/NZ, etc. then there isn't a lot you can do. For some people (including myself) a VPN helps reduce ping.

How can I make a (constructive) development suggestion?
Refer to the development suggestion subform
Suggestions are currently closed because we already have a lot on our plate currently. I will be bringing on a handful of new devs soon but, these things take time. Most of our devs are volunteers (including myself) or, maybe get some money here and there. They work on willard because they are passionate and want to contribute, not for the money.

What are devs working on right now?
Check out the development updates subform
Check out the #changelog section on the discord.

How can I become a dev?
Please refer to this post. Thanks.

What does Willard run on?
Willard runs on a highly modified version of Helix.
In itself, the Helix framework is a modification of NutScript.

Our modifications include:

1. Some public plugins (such as legs, containers, persisted props, etc),
2. Some modified public plugins (such as CIDs, antiafk, and radios).
3. A lot of custom things coded up from scratch.

All in all, Willard runs on nearly 300,000 lines of custom code written with love.

Please refer to the image on the right to learn more about the software stack that makes willard possible ->

Can you guys add (really cool addon X) to the server?
No.

Help! I lost (X) because my container disappeared.
Make a post in the refund section of the forums.

I lost an item after putting it in a bag inside of a container!
This is done at your own risk. You are not a guaranteed a refund if this happens, as it is an unintended mechanics and the logs do not accurately keep track of items in cases like this.

Can Willard admins really see everything?
Yes. We have comprehensive logging in place. This is used to resolve all kinds of disputes, as these logs are the single source of truth on the server for literally everything that happens IC.

Can I use the Willard Content for (X)?
Maybe. Please refer to this list of acceptable distribution of Willard assets:

1. For your own GMod server: Yes. This is 100% fine. We cannot guarantee that the assets will work as intended. There is a lot of custom code in there that makes these things work. No, we will not troubleshoot them for you. (unless you are a Willard community like Mythos or Short Stores)
2. For screenshots, SFM, etc: Yes. This is 100% fine.
3. To reupload elsewhere: Usually no. Ask Atle.
4. For a different entertainment medium (such as porting them to a different game): No, but perhaps we can work something out. Talk to Atle.

NOTE: If your use case is not listed here, or these answers do not satisfy you, reach out to Atle directly.

Will I get banned for (X)?
Depends. Usually if you have to ask, then its a yes. However, there are plenty of edge cases:

1. VPN/Proxy: This is fine in all cases.
2. Family Shared Steam Account: You CANNOT use a family shared account to alt on Willard. You CAN use one as a main. This essentially boils down to you having any characters between two steam accounts which share the same GMod license. If staff find out about you doing it, you will be banned. I might even write a plugin to do this automatically.
3. Use (x) exploit: NO. I will personally ban you for this. If you find an exploit, please let me know directly about it. We have systems which will ban you for using existing exploits so don't even try it. If you get banned for this, it will never be repealed.

Minimum Technical Specifications​

Just because you can run Sandbox does not mean you can run Willard. If you do not meet these requirements, you might experience instability:

1. GMod installed on an SSD!!! (m.2 preferred)
2. 2gb VRAM (4gb preferred, depends on resolution)
3. 2.5ghz CPU (3ghz preferred)
4. 8gb RAM (16gb preferred)
5. Display resolution 1600x900 (or higher)
6. An ethernet internet connection (preferably >50mb/s down 5mb/s up)
7. Windows 10/11 (haven't tested on linux but its probably fine)

 

[Neonity]

The technical FAQ received a tiny update, clarifying putting bags into containers.

In short, this is done at your own risk due to the nature of the bug.