eraser1

Thread locked. This is not the place to discuss/appeal your infiSTAR ban.

We have closed this thread and marked it as solved.

Thanks for the report!

Don't forget the leaflets! Everybody loves leaflets

https://github.com/Defent/DMS_Exile/wiki/Changelog#september-2-2017-1240-pm-cst-america

@johnyboy2o11 Just follow the instructions. It will automatically generate exceptions for your scripts.txt as scripts logs are created. It doesn't matter if you have any other mods or addons running.

We still have upcoming changes and tweaks pending, don't you worry.

It's a framework for Many addons have been created to build on this framework to suit various play styles and scenarios.

Fixed, thanks

You might want to consider tweaking your basic.cfg

This is not the correct location to make a ban appeal for infistar. Either join his discord or make a ticket on his website. Thread locked.

Halp, mod no work

Keep in mind that "Better" UI tends to be subjective. Eichi was experimenting with a plethora of themes and designs before settling on the current one. He also did a lot of research and made decisions on the "requirements" for the UI before selecting it. If you don't like it, you're more than welcome to override the vanilla Exile UI.

Infistar typically relies on the presence of BE filters, at least for some of its functions, and uses them to complement its anti-hack features: neither BE Filters nor Infistar is a replacement for the other. Unfortunately, because Infistar only has access to script commands, it is fairly limited in scope of what it can do to detect/prevent cheaters (but @infiSTAR still makes the most of it). This is why the anti-hack comes with a set of BE filters you can use. I would say that if you aren't going to use the kicking function of most of the filters, that you at least log some things.

@[AI] Stalker That is incorrect due to a variety of reasons. The "fn_FillCrate" function is designed so that no modifications are needed to the script itself, thanks to the option to pass code (and its parameters) directly to the function. All you have to do is create a function that will return a list with 3 sets of values: Weapons, Items, and Backpacks. So if you had a list that defined "_crate_weapons_scopes", and you wanted to add each scope from that list one by one, you would do: private _weapons = []; private _items = []; private _backpacks = []; { _items pushBack _x; } forEach _crate_weapons_scopes; [ _weapons, _items, _backpacks ] You define and initialize the list of weapons, items, and backpacks at the top. No weapons or backpacks are added in this example, so they remain empty lists when they get to the bottom. Then the script simply cycles through "_crate_weapons_scopes" and adds each scope to the list of items. Finally, at the bottom, the values are "returned" to whatever script/function that called the script in the example. In this case, you would simply return a list with: "Weapons, Items, and Backpacks" in the form that DMS expects/requires. The fillCrate function will then handle the rest.