Our server pr0vider carried out maintenance on 15 January 2020 but it corrupted some files in the process. If you notice anything out of the ordinary (partial files, pages not loading, that kind of shit) then let us know at:

Browse Source

Updated HALP fiel to reflect new U5 defaults, also clarified some shit

Wazakindjes 1 year ago
parent
commit
bd50fc1a76
1 changed files with 10 additions and 5 deletions
  1. 10 5
      HALP.md

+ 10 - 5
HALP.md

@@ -4,7 +4,7 @@ Sometimes when using (a bunch of) modules, things get funky. Examples would be:
 * [Interference between modules, preventing correct functionality](#module-interference)
 * [Vague native error descriptions](#vague-errors)
 
-Also, I'm assuming you have at least __some__ basic knowledge of your operating system. If you don't and it's abundantly clear, I'll refuse to help you since you shouldn't really be running an IRCd in the first place. ;]
+Also, I'm assuming you have at least __some__ basic knowledge of your operating system. If you don't and it's abundantly clear, I'll probably refuse to help you since you shouldn't really be running an IRCd in the first place. ;]
 
 # IRCd crash
 In this case, do something like the following in your __Unreal user's shell session__ (or run the `apt-get` commands directly as root [I'm assuming Debian leenerx here]).
@@ -12,7 +12,7 @@ In this case, do something like the following in your __Unreal user's shell sess
     sudo apt-get install gdb
     /home/unreal/ircd/unrealircd backtrace
 
-I've never ran an IRCd on Windows so I don't know how to get a backtrace there. Perhaps via the GUI?
+I never run IRCds on Windows so I don't know how to get a backtrace there. Perhaps something via the GUI?
 
 The installdir (`/home/unreal/ircd`) may vary obv, you just have to point to the installed Unreal __wrapper__ (not the binary). You'll get some output like this:
     Core files available:
@@ -20,7 +20,7 @@ The installdir (`/home/unreal/ircd`) may vary obv, you just have to point to the
     -rw------- 1 unreal unreal 6903098 Oct 25 15:31 crash.report.core.1477402278.txt
     Type the name of the core file you want to research:
 
-You'll most likely want just the `core` file, but make sure that's actually when the crash occurred. Type the name and hit enter to receive a bunch of developer lingo. Now you can either find just the line that mentions one of my modules' names, or copy everything between the `START HERE` and `STOP HERE` markers (the latter is way more helpful tbh, although it __may contain sensitive data__). Then pass this info to me via one of the below [communication channels](#comm-channels). Be sure to use something like `pastebin.com` if you're passing on more than one line of output.
+You'll most likely want just the `core` file, but make sure that's actually when the crash occurred. Type the name and hit enter to receive a bunch of developer lingo. Now you can either find just the line that mentions one of my modules' names, or simply copy everything (the latter is way more helpful tbh, although it __may contain sensitive data__). Then pass this info to me via one of the below [communication channels](#comm-channels). Be sure to use something like `pastebin.com` if you're passing on more than one line of output.
 
 If what I said above is indistinguishable from Chinese to you, you can also provide me with access to the server causing the problem so I can take a looksie myself. =]
 
@@ -30,14 +30,19 @@ In case of functionality interference, you can use the same [communication chann
 # Vague errors
 I recently ran into a sort of vague error myself when writing a module using ModData: `No space available`
 
-Apparently that's caused when the available ModData slots are all used up. =] You can increase these if you want, but I'm not really sure if it's supported lel. You also have to do this on every server. Inside `include/struct.h` there are a few defines:
-    #define MODDATA_MAX_CLIENT 8
+Apparently that's caused when the available ModData slots are all used up. =] You can increase these if you want, but I'm not really sure if it's supported lel. You also have to do this on every server. Inside `include/config.h` there are a few defines:
+    #define MODDATA_MAX_CLIENT 12
+    #define MODDATA_MAX_LOCAL_CLIENT 8
     #define MODDATA_MAX_CHANNEL 8
     #define MODDATA_MAX_MEMBER 4
     #define MODDATA_MAX_MEMBERSHIP 4
+    #define MODDATA_MAX_LOCAL_VARIABLE 500
+    #define MODDATA_MAX_GLOBAL_VARIABLE 500
 
 It should be clear what to do here. =] I personally multiplied all of them so I should be good for a while. Recompile and restart the IRCd to actually make it work (again, on __all__ servers).
 
+__A much better way would be to harass me about the error you're getting and I can try to get the limits increased by default__
+
 # Comm channels
 I can be found:
 * On the [UnrealIRCd.org forums](https://forums.unrealircd.org/memberlist.php?mode=viewprofile&u=49094)