Should improve client FPS while still allowing conditions and scripts to
be customized.
Some special vehicles like MV22, UH1Y, etc. have UserActions overwritten
in their configs, so please let me know if you find any others that do
not get the option to repair or salvage because UserActions is
overwritten in their config. I think I got them all.
Vanilla commits:
a8c4238c0c350d73abe1
These will probably need some additional exceptions and corrections.
Please post the scripts.log entry if you get any kicks or logs that are
not from custom changes or third party mods.
* Fix spelling mistake of classname DZ_Czech_Vest_Pouch
As per subject
* Fix typo from 1.0.5.1 and rename DZ_Czech_Vest_Puch to DZ_Czech_Vest_Pouch.
As per subject
* Fix typo from 1.0.5.1 and rename DZ_Czech_Vest_Puch to DZ_Czech_Vest_Pouch.
As per
* More typo SQL goodness
As per subject
- Safe inventory arrays are no longer sent over network to all machines
on server startup and on each lock/unlock
- Disabled user input then closed gear dialog during safe
lock/unlock/pack to block various duping methods.
- Moved safe creation, deletion and gear handling to server. This cuts
down on add[Magazine/Weapon/Backpack]Cargo, createVehicle and
deleteVehicle BE logs.
Avoids setVariable value restrictions for players with special
characters in their name.
Also avoids issues with storing non-ASCII characters from player names
in DB inventory field.
@icomrade - In regex character classes only match each single character.
So a range with more than one character on one end (20) won't work:
http://www.regular-expressions.info/charclass.html
You can see that by running this code in-game with your old filter and
it will kick you:
player setVariable ["hit_glass3",1,true];
Adding the + on the end makes it match the character class one or more
times, so now it will match any integer >= 0.
The big list of removals in setvariableval.txt and publicvariableval.txt
were duplicates. Other removals are covered by the new regex filter.
Still needs work. If you encounter kicks please post the restriction
type and number along with the log line in the 1.0.6 testing issue.
