Search results

__author__ = 'DreTaX' __version__ = '1.0' import clr clr.AddReferenceByPartialName("Fougerite") import Fougerite class ZoneTest: def On_Command(self, Player, cmd, args): if cmd == "create": zone = World.CreateZone("TestZoneee") #DataStore.Add("Zones"...

Complete answer: Zone3D :p I will go and do a Zone3D test, and test the copy cat plugin. Will reply with an example so you can use Zone3D and you don't have to for cycle

DreTaX updated BannedPeople with a new update entry: Additions Read the rest of this update entry...

Modernised Console Event commands

1. Store the locations in an inifile. Add them to an array while you convert them to a vector. When a player deploys an object check the distance. 2. Zone3D. This is probably the best. https://github.com/Notulp/Fougerite/blob/master/Fougerite/Fougerite/Zone3D.cs I can send you an example code...

I can't actually tell what to do. Dunno. The problem is probably the for cycle, but ehh...

:rolleyes:

Nah. It's something that mike has to fix. DamageEvent spams my logs atm too.

Sqlite is functioning great. I didn't test It if It can be imported on the server though import sqlite3 conn = sqlite3.connect('test.db') print "Opened database successfully"; conn.execute('''CREATE TABLE BANS (NAME TEXT PRIMARY KEY NOT NULL, IP TEXT NOT NULL...

Bitchie @Snake still didn't convert it to sharp. https://github.com/dretax/Python-Plugins/blob/master/FougeritePlugins/NavMeshRunner/NavMeshRunner.py

I'm also interested using sqlite3.py. That might work a bit better than the ini files

I actually wonder If we could find the method where the server sends these RPC client id (xyz) was not found, we could just simply force it with a patch to disconnect a player.

Actually to be accurate there are many possibilities. Even from rust or fougerite. Having bugged npcs cause navmesh errors, which will spawn the console. 2. Having many objects with players and many plugins can also cause It sadly. I remember playing on official srvs, and when the server had...

I think having a single timer for this should be enough. But I get what you mean. The time. Yes you could check if the id in the ds exists, maybe the best would be in that place is the onplayrrconnected, instead of spawned. Just be sure to remove the player from the ds if he disconnects.

Lel. Well the only reason why I think Its not the problem, because the timer gets created in the Ipm module which wasnt updated. Do you have error and exception logging inabled in the Fougerite.cfg? So you want a timer which has an updated list all the time?

I believe RPC errors are caused by rust Itself. Why? Because the server fails to send a command to the client, and tries to send It again, instead of disconnecting the shitty player. You can try doing for example: Player.SendCommand("xyz") or player disconnection. You will get RPC errors...

I don't think that anything has to do with 1.0.8... Besides, not even with IPM. I don't see you are having a "Timer" callback at all. The timer is unlogical. You launch a timer with an empty dictionary. The timer already received the data, and will never update It from the variable. Since, you...

mhm. I actually have crashes, but the ds doesn't wipe itself.

We cant stop adding. Besides, use IdIdentifier if you want to check for cheaters. Sent from my Samsung Galaxy S4