Server Help :: View topic - SSC Biller problem (lvl2)

Server Help

General Questions - SSC Biller problem (lvl2)

Anonymous - Mon Feb 14, 2005 6:08 pm
Post subject: SSC Biller problem (lvl2)

I can login to SSC (lv2) BangOp, fine (confirm appears and all), and i cant ban for some reason i do:
?ban -e=365 NAME

and it replies

PlayerNot Found: NAME

it worked before not anymore, why?

Solo Ace - Mon Feb 14, 2005 6:13 pm
Post subject:

Use -e# to specify ban duration, not -e=#.

Gravitron - Mon Feb 14, 2005 6:43 pm
Post subject:

And these are the guys they give high level access.

'Nuff said.

Kthankx.

(and you wonder why the game is going to hell)

Solo Ace - Mon Feb 14, 2005 6:50 pm
Post subject:

Not to be rude, but, I thought exactly the same when I was writing my previous post in this thread.
I think I know who this is.

Anonymous - Mon Feb 14, 2005 7:25 pm
Post subject:

?ban -e365 NAME tried that still didnt work says PLayer Not Found

Cyan~Fire - Mon Feb 14, 2005 8:18 pm
Post subject:

Maybe the name's wrong.

Purge - Mon Feb 14, 2005 9:03 pm
Post subject:

It's ?ban -e#=NAME.

Anonymous - Mon Feb 14, 2005 9:10 pm
Post subject:

Still dosn't work name is perfect, no errors and purge ure way dosnt work either

D1st0rt - Tue Feb 15, 2005 12:05 am
Post subject:

*kill 348756234985623476583245763924875634765873242734657832456873456827345872345

CypherJF - Tue Feb 15, 2005 12:07 am
Post subject:

When in doubt, Swift is the BanG operator of SSC.

Gravitron - Tue Feb 15, 2005 3:34 am
Post subject:

*info
*trace
*addip
*addmachine
*kill

Enough said.
Learn it you newbs.

Mother of gravitons, a newb with lvl2 bang access, who need another newbs to tell him how to use it too, what a nightmare - for any game!

Purge - Tue Feb 15, 2005 7:14 am
Post subject:

I'm guessing that 'Guest' is Agurus.

Gravitron - Tue Feb 15, 2005 7:39 am
Post subject:

What zone is that newb from/modding at?

Mine GO BOOM - Tue Feb 15, 2005 9:23 am
Post subject:

Gravitron wrote:

What zone is that newb from/modding at?

If they wish to remain anonymous, let them.

As to your question: BanG only keeps a short term history (something like 200-500 users) of people who've entered your zone. So if you try to ban a username that is not either currently in the zone, or in this history, it won't work.

If you really need to ban this user, get a hold of one of the billing admins, and they will be able to find the needed information to enact a ban. Or have your zone's sysop send me an email.

Gravitron - Tue Feb 15, 2005 10:50 am
Post subject:

You let them...

...while I expose them!

Anonymous - Tue Feb 15, 2005 1:57 pm
Post subject:

Yeah, I would think this would be Agurus, all right...

If it is: Ask Beef how to do it.

If it's someone else:

Either get help from a big guy at SSC, or figure out how to do it on your own. (Without all these bums.

)

Solo Ace - Tue Feb 15, 2005 2:19 pm
Post subject:

Bums? Okay then Mr "Freakman Bob".

MGB's right, but I think you should be able to figure out how to ban someone without depending on SSC's history info if you're at that level.

Gravitron - Tue Feb 15, 2005 3:24 pm
Post subject:

You can give a stupid ban power, but you can't take the newbie out of him.

Cyan~Fire - Tue Feb 15, 2005 3:56 pm
Post subject:

MGB (commands.txt) wrote:

?ban (command) (name) = Adds ban to player, with extra commands if listed. (4+)
Commands:
-* = Adds to network ban list (1+)
-! = ban all logins from IP range, new and old accounts (2+)
-e# = Changes day count of ban, each level has max different, default = 7 (4+)
-a# = Changes access remove. Can only # be your level or lower, default = 4 (4+)
-i# = Changes ip# ban range, default = their IP# (3+)
-m# = Changes the ipmask for ban range (default: 255.255.255.0) (3+)<BR>
-n# = Changes id# ban, default = their ID# (3+)
-k = Doesn't kick player off the instant ban takes place (4+)
-z<zonename> = Bans the player in that zone instead of current one (have to be both zone's bang op)<br>
-c = Removes the id# for the ban (such as if they randomize mID) (4+)

Purge - Tue Feb 15, 2005 8:52 pm
Post subject:

Indeed, what I said for e#.

Solo Ace - Wed Feb 16, 2005 2:01 am
Post subject:

What you said for -e# is incorrect, the '=' isn't part of the command.

Anonymous - Wed Feb 16, 2005 11:21 am
Post subject:

I just can't believe that someone actually owns a zone on SSC and can't figure this out.

Anyway....

*kill is much simpler and faster - I've seen it used effectively many times now.

Anonymous - Wed Feb 16, 2005 2:36 pm
Post subject:

I can't believe BanG is actually so *cough* that it does thing like this...

Solo Ace - Wed Feb 16, 2005 4:34 pm
Post subject:

So you'd want BanG to keep all data required for a ban?
It's something you'll have to deal with.
If you really want to ban a person, you shouldn't fully depend on the data BanG recorded.

Freakman Bob wrote:

I just can't believe that someone actually owns a zone on SSC and can't figure this out.

I can't either; It's sad, we figured that out already.

As for your kill idea: *kill doesn't do what BanG does, and it's less, less effective than BanG.
Also, it wouldn't have helped him in any way.

Gravitron - Wed Feb 16, 2005 6:19 pm
Post subject:

Back at my days, we simply *info'ed everyone (new person that is to say) who entered the zone, kept detailed lists of that.
Manually compred data if it was called for.
Sure it was less efficient, (BanG does it for you) but it worked.
And we sure didn't need to wait for no billing op to ban for us, or find who someone was when he used another alias for cheating or whatever.
Didn't need no BanG, just *kill, *addip, *addmachine, it more than did the trick.

Cyan~Fire - Wed Feb 16, 2005 7:15 pm
Post subject:

Wait, if every mod in a zone has billing ?ban power, how is that any better than the system you just described?

Gravitron - Thu Feb 17, 2005 5:43 am
Post subject:

Because it is more intuitive, it also does macID ban, IP ban, without allowing a mod to do stupid mistakes or intentionally abuse these ban types (sysop level only) IE entering a wide range of IPs and macIDs.
(FYI : Kill bans the specific user macID).
It also places a hook in your registery, matches timezoneBIAS and other shit.
Basically it automates (isn't that what apps/scripts are for after all?) a whole host of functions you will have to "hire" peoeple to do for you or work your ass off to do it yourself.

P.S.
I never said BanG is bad, it's not half bad at all as said it saves a lot of time and offer advanced access while retaining zone heirarchy and secure users from easy abuse.
But, however, it's who controls and has access to it that is bad.
Which makes the entire ordeal just...SAD.

It's like saying, Satan now has the power to ressurect your loved ones, well woopie A and all that, but the price you'll have to pay is that once they die again both you and their souls is his to throw to hell...
Where's the overall good in that bigger picture?

Anonymous - Thu Feb 17, 2005 2:02 pm
Post subject:

OK, BanG is better. True.

But that's sort of off-topic. Heh, my comment was anyway...

Anonymous - Fri Mar 04, 2005 10:00 pm
Post subject:

Quote:

The *addip command no longer works. And "back in the day" there was no effective way of banning people. What i had to do and from what i am told what BD Vine did for the first version of bang was make a batch file that you could simply add the ip you wanted banned and have it banned accrossed multiple zones. However of course to make it useful you would have to ban a large range of ips to stop them from entering

I remember when A friend of catids i forget his name made a bot that recorded the aliases and infoed them all which made for a awsome Ban bot. That was the next step for players and zones without bang access

I think that more data needs to be pulled that can uniquly identify people and add it into bang to make it that much harder to bypass it.

CypherJF - Fri Mar 04, 2005 10:51 pm
Post subject:

the ban on maucaub's biller was harsher than SSC's to bypass... not so sure about catids..

Gravitron - Sat Mar 05, 2005 10:59 am
Post subject:

BDvine didn't create no special-unique batchfile (the person was a complete nimrod FYI).
It was a text file that *addip used to create, which even after SSC disabled the command, you could still make use of said file.
BlockIP.txt for *addip and BlockID for *addmachine.
Both could still easily be manualy created via the windows GUI and have values put onto them.
You could gain the values by issuing *info on a person.
Once the person's information been put to file, *kill to kick him off the zone and that was the end of him.

And trust me, for the few occasions it had happened, when Jeff wanted someone off the network, he stayed off the network.
Unless, as with BanG, he got a new PC and and a new IP range.
So "back in the day", if you had the knowledge, you could effectively ban as you can today.

Today's ban system is simply more efficient, is all.
As I have said before, it does exactly all that we have been doing manually, only that it automates it, as well as add a few more things to track after.
It is still not infallible.