Search results

There are no inifiles in JintPlugin

removing a line that was commented out fixed a problem? :O

He wants someone to upload the server files (its not a warez site...)

Just look how I "recorded" and spawned the "shop" here (~3:15): the trick is rotating every piece

MagmaPlugin has a new "Data" class: https://github.com/fougerite/Fougerite/blob/master/MagmaPlugin/Data.cs AddTableValue - DS wrapper GetTableValue - DS wrapper GetConfigValue - gets the config value from a .cfg file (just like in magma, so it should work)

anticheat stores vector3s in the ds, you shouldn't use DataStore.Save()

args is not a javascript array, it's a c# array, you should be able to do it in js: var nuStr = String.Join(" ", args); or var nuStr = System.String.Join(" ", args); http://msdn.microsoft.com/en-us/library/57a79xd0(v=vs.110).aspx

Probably I could do it better know that I worked with unity, but I have other projects now. ( and I bet Mike can do it better anyways ;) )

I don't think there is anything wrong with the interpreter, most likely he was missing argsToText() function from the script

try without rustentials

'- In the terminal, I enter "-1"' make a shortcut and add "-1" to that

You know, in the other thread sum1 said, that the players can't stop identfying things

you can store values in the datastore as boolean: function On_Command(Player, cmd, args){ if(Player.Admin&& args.Length==1){ switch(cmd){ case"addmod": DataStore.Add("Moderators", args[0],true); Player.Message("Player with the id "+ args[0]+" added to...

O.o what's the purpose of that? Storing non-serializable data(fougerite.player) in the ds is not too safe and also you have Server.Players and PlayerClient.All properties (safer, faster)

yep, that's a rustpp thing, but in this case he should mention that rustpp is needed, and admins must have rcon flag

also, the player can't be .Admin when it just connected, Player.Admin is true when the player is logged into rcon

In magma you should be able to: var path = Plugin.Path; var path = path.Replace("MyPluginName", "OtherPluginName"); var path = path.Replace("MyPluginName", "OtherPlugin'sIniName");

Jint = javascript interpreter 2.2 = the newest version magma uses 0.9.3, but jint was rewritten from scratch magma used one engine with one scope for every plugin and compiled the code before running a function, jintplugin module uses one engine and one scope per plugin, and compiles the code...

On a side note: you can't use other plugin's function, each plugin has its own scope (not like in magma)

that's what datastore is for