Thom McGrath

Sorry @RudiVuuren, that was intended for the original reporter.

Yep, same crash as everybody else. It doesn't even look to be loot related, as it's crashing while loading a material. I have switched Beacon to use class strings again....

In %AppData%\The ZAZ\Beacon there is an Events.log file. Can’t you post that here so I can potentially see more details?

I’m not trying to be a jerk, but that’s not good enough. With the information I have here, there’s nothing I can do. That file may help.

Should be fine. The weights are relative to each other. 2 entries with 100 weight are the same as 2 entries with 0 weight. I could probably compute the chance...

I do something similar for my own server, except I have presets for each weapon. Even some variants such as a "combat longneck", "sleepy longneck", and "shocky longneck." These presets...

You're welcome. My hesitation for your specific suggestion comes from two things: I really dislike "special knowledge" type features, and the comma could seem odd to users whose decimal separator...

No, not exactly. Beacon is specifically designed to counteract the loot source multipliers. So the act of bringing the default table into Beacon ends up nuking the quality. The author...

Presets are saved in %AppData%\The ZAZ\Beacon\Presets on Windows and ~/Library/Application Support/The ZAZ/Beacon/Presets on Mac. Although Beacon supports "unknown" class strings, adding information about those classes is not something currently supported....

What’s not working properly about them?