Poll

.

.
0 (0%)
.
0 (0%)

Total Members Voted: 0

Author Topic: Boss Battles - Six years...  (Read 1984115 times)

I was recently banned for "team-killing sentry guns". I either did not do this, and if I did I was unaware because I was using a rocket launcher and constantly firing at the boss. Next thing I know, someone is complaining that I intentionally destroyed his sentry gun. I apologized several times and was banned anyway. 

I dont think that anyone that is not the boss can even harm a sentry gun.
However, medics can heal them. Were you shooting rockets anywhere near the turret or was it the dark bedroom version?

I dont think that anyone that is not the boss can even harm a sentry gun.
However, medics can heal them. Were you shooting rockets anywhere near the turret or was it the dark bedroom version?
Anyone can damage a sentry.

However, medics can heal [sentry guns].
by the way, i tried healing one the other day and it was like someone tried preventing that, because it would stop every other time you tried.
Or was that just me?

How about this:
a person joins.
they start playing.
The same person joins again (multiclients)
If the person is not on the exception list or a admin/super admin:
the first one is kicked, and the second one is unaffected.

That would prevent troubles with people that have crashed or lagged out.
Any problems with that? It's 100% doable.
this is pretty dumb IMO, if there's an admin on and you can tell that the person is either multiclienting or just crashed kick the first one. It's not rare for relatives to play using the same key, hell, at one time it was me, my brother, and my cousin all playing my key on my server.

this is pretty dumb IMO, if there's an admin on and you can tell that the person is either multiclienting or just crashed kick the first one. It's not rare for relatives to play using the same key, hell, at one time it was me, my brother, and my cousin all playing my key on my server.
That's what I told him.

Same, it's a really stupid idea.

Pecon, I have an idea that might fix a lot of problems with Kaje: Instead of dropping the player into the mech, turn the player into the mech, and spawn a random bot as the driver. It would fix both the fact that Kaje can't be damaged because apparently the vehicle isn't part of the minigame or something, and the possibility of a dumb player ejecting themselves from the mech. (Though admittedly that second scenario is pretty funny.) To top it all off, the damage done to the boss would be shown onscreen.  It would also look exactly the same to the players.

However, we haven't really used Kaje without an invincible mech. It may require a new datablock with higher or lower health for balance.


this is pretty dumb IMO, if there's an admin on and you can tell that the person is either multiclienting or just crashed kick the first one. It's not rare for relatives to play using the same key, hell, at one time it was me, my brother, and my cousin all playing my key on my server.
That's what I told him.
Same, it's a really stupid idea.
Could you please read my posts before posting that?

In short:
Its not going to have any negative affect on the server,
It will be easy to use,
It will prevent multi-clienting before it happens,

It will have an exception system,
It will be toggleable through a RTB pref,
It will make the admins jobs easier.

if you want to be added to the exception system once its done, just ask a super admin and they can decide wether or not to add you.

EDIT: I found what was wrong with my code, I had a syntax error. Silly me!
« Last Edit: December 12, 2011, 01:01:49 PM by Ipquarx »

Jets, your idea will not work because when the player is the mech, they cannot fire.
I've tried turning myself into the mech both via eval and events, and another player via eval
the player could move but not fire

Jets, your idea will not work because when the player is the mech, they cannot fire.
I've tried turning myself into the mech both via eval and events, and another player via eval
the player could move but not fire
Hmm. I'll look at the script later. There might be an easy solution to that.

Could you set it to be constantly firing?  Then the player would just look where they want it to shoot.

Allright, my code's all fixed up.
I'll send it to pecon when i get home.

Allright, my code's all fixed up.
I'll send it to pecon when i get home.
or jetz