Matthew Hively

The way the documentation is worded, it almost seems like it should have a "bad example" and a "good example". So the wording is warning you about something, that isn't...

I wish this would get merged, the `ALTER TABLE` statements executed every boot is anoying.

I'm positive its not a fixed work cycle. I've been playing the GoG version recently, and although I haven't been exactly timing things I know for a fact: A) Not...

I see. I guess it was my understanding that any changes from S2 dos version to RTTR were to be options that could be toggled on or off. Obviously not...

Gotcha. I'll do some more checking. See how many jobs are afflicted with this issue. Verify that woodcutter and forester behave differently... etc It seems odd to me that some...

Unfortunately no, I have become sidetracked by other projects. This is still on my todo list when I circle back to playing settlers 2.

I got this same issue. it was resolved by updating `$DefaultLACreate` and `$DefaultLACEnable` to true in the config script.

Should be fixed by Resque 2.3.0 Not quite out yet.

Looks like not everything is fixed by resque 2.3.0 Still receiving these even after upgrading to Resque 2.3.0 & redis-namespace 1.9.0

I also see this warning raised now too: `Redis#sadd will always return an Integer in Redis 5.0.0. Use Redis#sadd? instead.(called from: ~/.rvm/gems/ruby-2.5.7/gems/redis-namespace-1.9.0/lib/redis/namespace.rb:479:in 'call_with_namespace')` ``` # Dispatch the command to Redis...