In case you don't know what NeoAnticrash is, you can get it off of J2O right here.

I uploaded a new version (version 1.1) just a few minutes ago, so I suggest that those of you who have been using this go and get the new version. It fixes at least one important issue. I also tried adding support for Windows 95/98/Me, but seeing as I don't have any of those versions of Windows available at the moment, I need someone else to try it out.

This thread is so I can get some feedback from you, and let you know my progress on the program. So tell me what you think, or anything odd you have noticed. Right now the purpose of the program is to prevent your server from crashing, but I am planning on expanding this to do stuff like provide a chat log and give it a nicer interface and do stuff like that, just so you know.

I'll be able to test Windows 2000ness tommorow. Cheers.

There shouldn't be any problems on Win2K since that's what I'm using to make this. But let me know if you are having problems.

I just realized that I forgot to mention that version 1.1 includes built-in weapon regeneration (respawn). I haven't heard of any reports of there being weapon regeneration issues on the Battle Server, so I assume it is working.

Awesome program, Mono. Now I don't have to bother making a .zip of the latest AntiCrash.

Hey Mono! Let me know if you need to test that program. I'd be happy to crash your server give you some assistance ;P

Yeah, especially because there's a new way of crashing, which should be stopped.. :P

Thanks for the offer, Overlord. It is helpful having someone who can consistantly crash me and tell me what they're doing.

Oh, and I should have another small update in about a day or two.

I can help in the same way as Overlord if you like (I already managed to break through the old version at least without lasers).

Well, I guess I could find another glitch than the one I already reported, if I set my mind to it, so I am up for it :0

Well the way I crashed the old one still works and this time it doesn't even tell me who did it =P

Unless my filter is broken, the anti-chat hacking seems to work fine.

EDIT: Perhaps you can also make it filter bad words out of the chat.
EDIT2: Haven't tested this yet so in case you've put it in already don't mind... You could make it so that players who didn't specify the proper server password for private servers cannot join.

No you shouldn't. Then I can't play private games without CTOing.

Unless you create a joining utility that allows for entering a password, too

But it would save the annoyance of people entering your test servers (yeah blah blah player limits blah blah)

Originally Posted by Fquist

Unless you create a joining utility that allows for entering a password, too

JazzForce

yes of course, EXCEPT THAT IT DOESNT WORK

Stijn: Offensive context

I need a way of finding you guys when I could actually use testing. :P

Jam, I think I have the problem you showed me mostly worked out.

Grytolle, I haven't had a chance to test the problem you showed me, but I might have covered it working out other problems.

Overlord, I don't think I'm going to bother with cencoring due to it's futality, at least not at this point. Maybe in the future when I can make it an option. I would like to cover the password thing, but I don't know how I would go about that.

Originally Posted by Monolith

Overlord, I don't think I'm going to bother with cencoring due to it's futality, at least not at this point. Maybe in the future when I can make it an option. I would like to cover the password thing, but I don't know how I would go about that.

No man - no.

Originally Posted by Monolith

I need a way of finding you guys when I could actually use testing. :P

I'm on ICQ most of the time while online and sometimes you can find me in jj2 servers when I'm testing and debugging the final public beta of Controller v4.1.

Originally Posted by Monolith

Overlord, I don't think I'm going to bother with cencoring due to it's futality, at least not at this point. Maybe in the future when I can make it an option. I would like to cover the password thing, but I don't know how I would go about that.

The bad word filter shouldn't be that difficult to do. You could make it read a txt file where each new line inside the file is a different word to filter (excluding comments that begin on ; and blank lines). This also gives the option to disable the filter whenever the text file is empty or doesn't exist. You could later give an extra option when you make the gui.

Regarding the password thing you could make the program check whether the server is private or public at this address: &H5FCCEA for 1.21 and &H62030A for TSF and (in case server is private) automatically block any join packets (0F) that follow from the same client who didn't specify a password. You can see if a player specifies a password by some UDP packets that server receives and then sends a "go ahead" or a "no go" packet back to the client depending whether the correct password was entered. PS. You can read the password from the following address: &H5FB1C8 for 1.21 and &H61E7E8 for TSF.

Make that be a choice you can disable =/

Originally Posted by Overlord

bad word filter

Doesn't JJ2 have that built-in with filter.lst?

Not server-side.

If you make that PW filter thing, I cto 90% of the times in private servers too. I wouldnt really like that
I would like something else in it, now it logges chats only.. how about logging times with it, and scores with it too? :P Then JJ2WC3 has its logging program it wants, which registers scores (kills maybe too?:P) and chats

I was just accused for chat hacking by a person called Kasia and got banned from his\her\its server. Great. He\she said that NeoAC reported me or something, and I've seriously done nothing.

Thank you for the details, Overlord. The password thing would still be difficult to get working since I don't have all the pieces yet, but it sounds like people at least want it to be optional. The idea of using a file for the filtering sounds good.

ThA BLiNG BLiNG RaBBiT, there had been a problem where NeoAC reported chat hacking in certain cases if there was someone playing split-screen in the same server. I have fixed this, although I can't remember if it's part of 1.1. But it will be fixed in the next version I release.

NeoAntiCrash version 1.2 is now available. You can get it in the same place, right here. Report any problems you notice directly to me (preferably), otherwise any comments or requests can go here.

Okay..
When I start a server at jj2, and open NeoAC, I get an error.
"failed to create the named pipe server"
It does NOT log chats, nor it logs which IP attacks me.
I wonder if its only me who gets that error ;P
Anyways, good things: I cant be crashed at all anymore, not even with 2! MegaNukes running. lol, my computer lagged badly, but jj2 kept running :P

Meganuke still freezes my JJ2 with the new NeoAC running =(

Vegito, what OS are you running?

Jam, I tested it with MegaNuke over and over again. ;(

Something still crashed the Battle Server. If you know what it is, leave me a message.

Im running windows XP.
Meganuke doesnt seem to crash me, even when I ran 2 nukes at the same time...

Weird, I'll double check..

EDIT: You're right, it does prevent the crash- but JJ2 did lag like hell meaning I thought it had frozen (could be because meganuke uses 100% CPU, I'll try it across 2 computers later).

I dunno what meganuke is but neoac sounds good

Originally Posted by Jerrythabest

I dunno what meganuke is but neoac sounds good

Meganuke sounds better

Just crashed Vegito through NeoAC 1.2 with nothing but plain ol' MegaNuke.

Indeed, NeoAC adds the IP to the block list, but then after that I get crashed, rofl :P

Vegito was unable to crash me back in the same way however-

> Bad data from 62.234.x.x. Malformed packet. Sub-packet goes beyond the p
acket received.
> Bad data from 62.234.x.x. Malformed packet. Sub-packet too short.
> Bad data from 62.234.x.x. Malformed packet. Sub-packet too short.
> Bad data from 62.234.x.x. Malformed packet. Sub-packet too short.
> Bad data from 62.234.x.x. Malformed packet. Sub-packet too short.
> Bad data from 62.234.x.x. Malformed packet. Sub-packet too short.
> Added 62.234.x.x. to the block list.

Then nothing happened. I am using 1.25i if that makes any difference..

In this context, "work in progress" means that the ability for it to work is in progress. I made an XviD-encoded video which is watchable here.

Try releasing it after it works next time.

oh btw, this time logging worked o.O

I will test further as I get the chance.

Originally Posted by DaPete10

In this context, "work in progress" means that the ability for it to work is in progress. I made an XviD-encoded video which is watchable here.

Try releasing it after it works next time.

Stop trolling and go home, kid.