search

tictaczep / darkrp

Automatically exported from code.google.com/p/darkrp
0 stars 0 forks source link

Bannedprops.lua not working? #233

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
For awhile now I've never seen bannedprops.lua working and always had to
use uppl with ulx. May be something wrong with my bannedprops file, but i
doubt it as the default svn one has the same layout and doesn't work either.

Here's a copy of mine just for an example. 
http://pastebin.com/0EwrBeNk

Original issue reported on code.google.com by c_u_late...@hotmail.com on 24 Feb 2010 at 5:41

GoogleCodeExporter commented 8 years ago 
Also one with the door ram. I fixed this on my server, but for others this can 
lead
to major door glitching, if you use the door ram on an unowned door it sometimes
glitches it.

Simple as adding one line of coding;

                if trace.Entity:IsDoor() and trace.Entity.DoorData.NonOwnable then
        Notify(self.Owner, 1, 5, "You cannot use the battering ram on this type of
door!")

Original comment by c_u_late...@hotmail.com on 24 Feb 2010 at 6:02

GoogleCodeExporter commented 8 years ago 
rp_bannedprops 1
rp_allowedprosp 0

They work fine everywhere else.

define "glitches it"

Original comment by fpeijnen...@gmail.com on 24 Feb 2010 at 6:42

GoogleCodeExporter commented 8 years ago 
Tried both, didn't work for me

And, sometimes when you ram them, they become glitched and look open/closed 
when they
are the opposite.

Original comment by c_u_late...@hotmail.com on 24 Feb 2010 at 8:08

GoogleCodeExporter commented 8 years ago 
I tested the banned props in both my and a french server with the latest SVN. 
In both 
servers it worked.

Original comment by fpeijnen...@gmail.com on 24 Feb 2010 at 3:23

GoogleCodeExporter commented 8 years ago 
I also went to downtown and tried to use the battering ram on every single 
door. Some 
doors multiple times. The bug did not occur.

I think this bug is a source engine bug that was created in the last update.

Original comment by fpeijnen...@gmail.com on 24 Feb 2010 at 5:50

GoogleCodeExporter commented 8 years ago 
I see.

Well ive set 

rp_bannedprops 1
rp_allowedprosp 0

And my bannedprops file is http://pastebin.com/0EwrBeNk and its never worked 
for me.
Ill have to look into it.

Original comment by c_u_late...@hotmail.com on 24 Feb 2010 at 9:28

GoogleCodeExporter commented 8 years ago 
Please do.

Original comment by fpeijnen...@gmail.com on 25 Feb 2010 at 3:41

GoogleCodeExporter commented 8 years ago 
My banned props isn't working anymore either it just started

Original comment by Bigtyler...@gmail.com on 2 Mar 2010 at 9:47

GoogleCodeExporter commented 8 years ago 
Can you show me a copy of your bannedprops.lua? So i can compare.

Original comment by c_u_late...@hotmail.com on 3 Mar 2010 at 3:42

GoogleCodeExporter commented 8 years ago 
uploaded banlist works fine for me.

Original comment by fpeijnen...@gmail.com on 3 Mar 2010 at 9:46

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
This is my bannedprops.lua http://pastebin.com/PpCW60n9

Original comment by Bigtyler...@gmail.com on 3 Mar 2010 at 10:55

GoogleCodeExporter commented 8 years ago 
try 
rp_bannedprops 0
rp_bannedprops 1

Maybe setting it to 0 first before setting it to 1 again works?

Original comment by fpeijnen...@gmail.com on 4 Mar 2010 at 5:48

GoogleCodeExporter commented 8 years ago 
That doesn't work.....im gonna readd darkrp see if that fix's it

Original comment by Bigtyler...@gmail.com on 4 Mar 2010 at 7:54

GoogleCodeExporter commented 8 years ago 
After the latest DarkRP update, bannedprops.lua seems to work again, but i know 
for a
fact after looking at the latest two svn updates they had nothing to do with it.

Weird, but one more problem solved.

Original comment by c_u_late...@hotmail.com on 8 Mar 2010 at 10:59

GoogleCodeExporter commented 8 years ago

Original comment by fpeijnen...@gmail.com on 8 Mar 2010 at 4:00