SABOTAGE! Eliminating it possible or not?

[SquareEyes]

Hey all,

Last night I was having a nice quite game, MPI Instant Iceberg, looking out for anything odd to report. Built up my base & forces & taking control of the map & getting ready for the last big push. Next thing I know 2 or 3 losers join & start pushing all my tracked units into the drink. So I kick one & am about to kick the next & the whole game crashes to desktop like I hadn't been playing a game at all.

This is my second game since being back & it gets trashed like Commando or Red Devil warned me had been happening. Not a good start.

So is there anything I can do to stop these douche bags? Have the community implemented any strategies to overcome this problem? Obviously I could password my game but would this stop them? & even if passwords stop the aholes it also stops the good guys too. I thought I could send a password to a select group of trusted players that could be expanded on over time as a possible work around but it really limits who can join.

What say you???

[Red Devil]

get a rope

[GSH]

Your quest is this: get IP addresses of joiners. And if it crashes, send in the battlezone.log file -- found in My Documents\My Games\Battlezone II\Battlezone.log on Vista/Win7/8 -- to me. If you launch BZ2 again, it'll overwrite the battlezone.log file. If you have the (inane) Windows default of hiding file extensions, it'll just be shown as "Battlezone"

-- GSH

[SquareEyes]

Challenge excepted! Let the quest begin!

What's the best way to harvest heads ie. get IP addresses???

I feel like I have been deputised!

[Apollo]

Could always have people contact you over team speak 3 before you let them in the game.

[Commando]

I'm going to go out on a limb and guess that one of the IPs starts with 194.45.228.*. That entry is already in the banlist, you just have to delete the // to enable the ban.

[Commando]

Here is my current banlist.ini content.

[UserPrefs]

// Bans for specified addresses. To use these, you must fill in the
// address (replacing the "aaa.bbb.ccc.ddd/eee"), and uncomment it
// (remove the // from the start of it). No support is currently
// present for unbanning while BZ2 is running. Items in the following
// list may be commented out; subsequent items will be read. More IPs
// may be bannable that there are lines here; the exact number is
// undisclosed.
//
// The /eee component is a netmask of how many bits of the first part
// are checked. If it is 32 (default), the IP must match exactly. If
// it is 24, it is as if the 'ddd' component was wildcarded -- some
// would write 'aaa.bbb.ccc.ddd/24' as 'aaa.bbb.ccc.*'. If it is /16,
// then it blocks aaa.bbb.* . If the netmask is 0 (not recommended),
// it'll block every IP (not recommended).
//
// If you're confused as to how netmasks work, see
// http://en.wikipedia.org/wiki/Subnetwork , or use
// http://jodies.de/ipcalc or http://www.subnetmask.info/ for some
// online calculators
//

BanIP1 = "176.56.275.144/24" // a##violoator's IP. Used 176.56.174.144 and 176.56.174.87
BanIP2 = "216.177.129.152/24" // Confirmed AnchorFree IP. Confirmed through using it.
// Some recommendations from the forums. Remove the // from these
// lines to use them:

BanIP3 = "194.45.228.126/24" // Muffin
// BanIP4 = "69.180.10.90/24" // Sly pretending to be Nielk1 in game, see https://dl.dropboxusercontent.com/u/520 ... ist/IP.htm

// [...] // More BanIP### entries are possible


List updated. Didn't realize that the three new anchorfree IP ranges had been added to the proxylist. Deleted the duplicate entries.

[MrTwosheds]

Maybe the // should go missing for a few patches

[Commando]

I wouldn't be opposed to that.

[Red Spot]

Most frequent/abusive ingame griefer are:
Sly
Vearie
Feared

Feared isnt much of a problem though, he just follows the other 2.

[General BlackDragon]

Vearie doesn't grief or play much anymore. And I don't think feared would do that, it was probably someone impersonating him.


I find it odd, Red Spot, that you failed to mention the biggest problem, Muffin/Fadango.

[GSH]

Names are a suggestion as to identity in BZ2. IP addresses are much more concrete, which is why I asked for them above. A griefer report without IPs or a crash log is not actionable to me.

-- GSH

[Red Spot]

Vearie doesn't grief or play much anymore. And I don't think feared would do that, it was probably someone impersonating him.


I find it odd, Red Spot, that you failed to mention the biggest problem, Muffin/Fadango.

Muffin has only become a problem since the last couple of weeks, thats nothing compared to the years of griefing veary has done and displayes on his youtube profile. I cant even understand you try to defend him.
Muffin has also only become a problem because he learned from above names and didnt know which way to turn when his beloved group turned on him for behaviour they display as a standard.
If you doubt Feared is part of it, I am a 100% sure. And incase you doubt me, I dont specifically name people when I am not 100% sure about the statements I make concerning them.

GSH,
I cant provide crash-logs, I can provide a fair number of chatlogs that display plenty of the nature of some within this community. Its mostly veary and sly though.

[Ded10c]

"You might believe me, but it's true because I know it is" ain't gonna cut it. I also find it hard to see F1 as one of the perpetrators. Like GSH said, names are useless without IPs to back them up (better still, names to back the IPs up).

[Feared_1]

HAHA WHAT!!!? I haven't even CLICKED on my BZ2 icon (any of them) in at least two weeks. I'm a little busy at the moment.

Thanks for the attention, though.