Search results

MODERATOR POWERS DO YOU USE THEM

I should probably also generalize this for Vector2 and Vector4. And maybe Bounds (which are a pair of Vector3).

This problem is fixed in master branch and will be in my next MC release. Anticheat stores Vector3 objects temporarily in the DataStore. They don't actually need to be saved when the server shuts down. But Vector3 does not implement or inherit a serializer. So the Hashtable is corrupted when...

It's perfectly OK to leave checked "Use MSBuild". I use Xamarin for Fougerite development, and I leave it checked.

Yes, that's what I thought he meant. Oxide and Essentials are doing automatic updates?

Your posts looked like drunk texting, to be honest... :p

Can I quote you on that?

Friendly reminder: If you are running the GlitchFix module, make sure you disable rampfix in Rust++.cfg. rampfix=false rampgiveback=false

Good advice, Dretax. try / catch is a good tool. Don't rely on it too heavily though. There is some significant overhead, and there are some things you can't do in the vicinity of a try /catch block. There's also the handy ignore argument to catch, when you can't do anything about the...

I Wonder Who Pays The Bills For This Site

Thanks a bunch xEnt! I'm going to make that into a C# module. I think there might be a race on to see which of us can make that happen in Fougerite first! :)

function GetNameByOwnerID(OwnerID) { var ownerName = DataStore.Get("buildcalc_names", OwnerID); if(ownerName != undefined) Use if(ownerName != null). The DataStore will never give you a Javascript undefined value. It will give you a null value if the key or value don't exist...

Fixed! Save() and Load() the DS as much as you want. Vector3 are converted to/from strings going into DataStore, and will no longer cause it to blow up. You can also dump the contents of the DataStore to a ini file format to see what's in it.

It also removed the ability of the server admin to change Fougerite.cfg at GSP since rust_server_Data\ is not public. I split the cfg files for that reason. They've always been split in my builds. rust_server_Data\FougeriteDirectory.cfg is for the GSP to set a public folder and a private...

We aim to please. That was an easy one. :)

The Fix is In

New in MC1: Fixed Magma plugin.cfg loading. Rust++ uses its own name instead of Fougerite in chat response and notify. JintPlugin.dll is self-contained and can be enabled along with MagmaPlugin. Each uses its own folder for plugins, so there is no conflict. JintPlugin gets a new Lookup class...

mikec updated Fougerite MC with a new update entry: MC1_update Read the rest of this update entry...

mikec submitted a new resource: Fougerite MC - mikec's Fougerite builds, not official but should work Read more about this resource...

Since it's awkward to deal with Dictionaries and some other C# collections in Javascript under Jint2, I'm writing a new class for the JintPlugin that will make it much easier for scripts to manipulate collections of game objects. These are exclusive to Jint2, for now. Here's a sample of some...