Page 1 of 1

noclip problem? not big problem!

PostPosted: Tue Jan 10, 2012 00:31
by Nemo08
I think we may jast add to all solid nodes black posteffect. Without client modify it be works normal.

edit: damage on this nodes sometimes leads to a server crash or don't work (v20120106-01). bug??

PostPosted: Tue Jan 10, 2012 02:01
by dannydark
I personally think noclip should be removed completely or at least made permission based.

EDIT: I know server side flying prevention is on the todo list so maybe this will be done at the same time.

PostPosted: Tue Jan 10, 2012 03:25
by Nemo08
I know, this trick complitely don't solve problem, don't have premissions and so on, but it realistic and may be used on 0.4 servers right now without any server modifications

PostPosted: Tue Jan 10, 2012 12:58
by jordan4ibanez
dannydark wrote:I personally think noclip should be removed completely or at least made permission based.

EDIT: I know server side flying prevention is on the todo list so maybe this will be done at the same time.


dannydark i looked in the source..make the FLYING option dependant on the server

so lets put this into terms that anyone can understand..including me:

{

FLY = {get.fromserver}

if FLY == (true)

then

fly.allow (or whatever the flying init is)

if FLY == (false)

then
fly.deny (not allowing the player to fly)

and then have the init register whether or not the server can let you fly

FLY == the.init.script (for the flying)

}

hope some one makes it

PostPosted: Tue Jan 10, 2012 12:59
by jordan4ibanez
and then in the server config there will be a setting

FLY = true

or

FLY = false

PostPosted: Tue Jan 10, 2012 13:42
by xyz
jordan4ibanez wrote:
dannydark wrote:I personally think noclip should be removed completely or at least made permission based.

EDIT: I know server side flying prevention is on the todo list so maybe this will be done at the same time.


dannydark i looked in the source..make the FLYING option dependant on the server

so lets put this into terms that anyone can understand..including me:

{

FLY = {get.fromserver}

if FLY == (true)

then

fly.allow (or whatever the flying init is)

if FLY == (false)

then
fly.deny (not allowing the player to fly)

and then have the init register whether or not the server can let you fly

FLY == the.init.script (for the flying)

}

hope some one makes it

Yes, and if you talking about client modification - everybody who can modify client will still be able to fly.

PostPosted: Tue Jan 10, 2012 13:53
by jordan4ibanez
well then..what if we make it so that the server won't let them enter unless it detects that line of code? :)