Raid issues

• Putty is currently aware of this, I believe he's working on a fix. We'll update you on this as soon as we get word.
• We're still looking into it, Eil is currently away today so I'll try to get with him and discuss what the issue could be whenever he returns. It could be something easily fixable or something that will take dev time so there's nothing I can really tell you on this situation. Hopefully it's something easy that can be fixed quickly.
• Don't think this can be done, brought it up to Putty a while ago and it's like default spam filter or something that can't be fixed afaik.
• Mario looked into this in the beginning of the map, he couldn't find what specifically caused it and it's apparently just random so he couldn't deploy a fix. He's currently working on something else so this problem probably will not be fixed until we hopefully get new devs or dev time.

 

It just tracks 50/25 blocks off when you narrow. It's not completely broken, but I agree it needs to be fixed.

 

• What Anon said - We are aware, and are working on a fix.
• When trying to find the issue yourself, you said there was no identifiable pattern that you could find to it. This makes it rather hard to fix if we don't know what the problem is. Rest assured, we are looking into it.
• /go and /g conflicts with the anti-spam filter used on CTF/Build etc (/g, /global and such), so a specific work around for Raid would need to be made.
• Very complex bug, mario is currently very busy, so hasn't been able to devote much time to trying to fix this

It is only very slightly broken: On some occasions, it will track 25 (or 50 depending on the tracker) blocks extra than the length of the arm actually is - It is not major, only means that in some cases, the area needing to be mined in to find the base is larger. It is nowhere near 'completely' broken.