It occurs to me I might as well reply to this thread instead of just discussing its contents in private.

Originally Posted by Sir Ementaler

Could you please implement a command that lets admins check players' IP in a more polite way than kicking them off the server?

As in remote admins? I guess that wouldn't be too difficult; what do you want it for?

Originally Posted by Vivando

I believe this glitch is somewhat kind of a similar fashion, because it involves bullets shot while the player is moving diagonally, in slopes...

This is an old problem and much more general than the specific case you outlined. In short, a client destroying an object by shooting it does not register with the server unless the server and the player agree on where the bullet went. It's also really easy to demonstrate by setting up some trigger scenery. Unfortunately I don't think the chances are all that high of our getting to this one right away, since it's probably complicated and we really want to be done with this and take a break for a while.

Originally Posted by ColdMetal

Of course, this would all simply be an automated method of having /autostop set to ON and manually changing the map server-side, but I believe it would enhance the overall JJ2+ experience, as well as serve as a foundation for other innovations in the future.

Maybe if such levels actually got played, but with their very existence only hypothetical, I'm not convinced that the autostop+/c solution isn't good enough.

Originally Posted by Violet CLM

As in remote admins? I guess that wouldn't be too difficult; what do you want it for?

Yes. Sometimes, mischievous players are supposed to be temporarily banned from dedicated servers (e.g. for a period of 40 years), but bans are bypassed thanks to benefits of dynamic IP. It is possible to ban a range, but such a solution has serious disadvantages: it's possible that a few innocent players will get banned - which could be especially troubling in a server that is supposed to host JDC events - and ISPs not always (if ever) care to mention somewhere in the Internet what IP ranges belong to them, so it's likely that banning two known ranges will leave one or more unbanned. Surprisingly, it works the other way around, that is, having IP of a person you can easily check their ISP, which is often the only thing one needs to do to be assured that a suspiciously acting player with an unfamiliar nickname is the person they suspected them to be. Another case, sometimes occurring along with the former, is impersonation of existing players; I doubt I need to explain. Since player's IP is displayed when they happen to stand on the wrong side of a kick/ban command, I'm pretty sure it's not meant to remain a strict mystery to remote admins with access to those. Even if it is, it can be prevented thanks to admin.ini, so implementing the command shouldn't cause trouble.

Can't we just stuff those in the F9 list, just like for the server?

Originally Posted by Violet CLM

Maybe if such levels actually got played, but with their very existence only hypothetical, I'm not convinced that the autostop+/c solution isn't good enough.

I actually think this is doable via a different approach in the next Plus? Just need to write up a proof-of-concept to be sure.

Originally Posted by Jerrythabest

Can't we just stuff those in the F9 list, just like for the server?

It's a solution, yes, but you might want to limit it to admin groups which have it somehow enabled in admin.ini. In many dedicated servers literally everybody can have an admin password of some level so that they can organize matches, but letting them all see IPs is not necessarily a good thing. And probably not every host will want remote admins to check IPs anyway.

True. Then a command is the easier way of implementing it, since those have the authorisation stuff already taken care of.

Originally Posted by Violet CLM

This is an old problem and much more general than the specific case you outlined. In short, a client destroying an object by shooting it does not register with the server unless the server and the player agree on where the bullet went. It's also really easy to demonstrate by setting up some trigger scenery. Unfortunately I don't think the chances are all that high of our getting to this one right away, since it's probably complicated and we really want to be done with this and take a break for a while.

Okay so to be more precise, the problem is the increased chance to miss a shot from a target server-wise when running up a slope. Thanks for taking note anyway.

Thread unsticky and closed.

Continue discussion here please.