6cf740e7d4 caused undefined variable
errors since the variables were private in 2 places. _forced and
_recorddmg should be declared private in the top of the script where
they are defined, not in the compile.
* Updating german stringtable
The update for STR_ACTIONS_2TB and STR_ACTIONS_RFROMTB are important. That fixes a very old bug. It was no really readable in german because the words were a way to long.
* Add files via upload
* Fixing Desert Tent pack output
When packing a DesertTent the output was ItemDomeTent not ItemDesertTent
* Decreasing hotwire kit chance
* Decreasing hotwire kit chance
* Decreasing hotwire kit and combo lock chance
* Decreasing combo lock chance, fixing loot group
* Fixing loot group
* Lowering ammo box spawn chances again.
* Fixing Desert Tent pack output all versions
Vanilla commit:
804445830f
This was exiting with 0 damage if _hit=="". It accounts for vehicles not
being damaged at all when crashing full speed into walls. It was also
causing the player to sometimes glitch out of the vehicle or into the
ground when crashing as you noticed before @icomrade.
Also fixed driver getting a humanity hit for damaging passengers in
crash. Reverting 22b2a3a since this is more reliable.
If the gear sync script is called during the animation, the player will
fail the gear sync and not change clothes. After removing the anim this
no longer happens. Also I think this is a BS change that only
inconveniences the player and makes something that is already cumbersome
even more so
Vanilla commit:
e9b21a7e79
@icomrade we forgot to refresh keyboard_keys after the player changes
their controls in-game. The keyhandler was still using the old
keyboard_keys array since it is only set once at login time. The new
keys they set in-game wouldn't work until they relogged.
Everytime a piece of wood was spawned resulting from a chainsaw the
player would become more hungry and thirsty. Obviously in less than 10
seconds this would kill the player if they chopped multiple trees down.
Too many config variables made this unnecessarily complicated. Most
servers will want the defaults. For those that want to customize further
they can easily overwrite these files.
These seem like the most logical defaults to me. Allow all of these
people to manage and unlock by default:
- door owner
- plot owner
- plot friend
- plot admin
- door friend
- door admin
Door friends should be able to manage by default so they don't have to
wait for the owner to come back online to add someone as a door friend.
Plot friends and plot admins can get around the door by removing it and
building another one anyway, so locking them out is pointless. It is
still useful to have these as separate variables for servers that do not
require plot poles though.
Regular friendlies should not be included by default, since we have the
more fine grained plot friends and door friends lists for that. Regular
friendlies will probably be replaced by groups in the near future
anyway.
Please post a comment if there are any issues with these defaults I'm
forgetting. Thanks.
Only the owner, plot owner, plot friends and plot admins should be able
to see the plot boundary. Randoms just use it for griefing.
Also renamed the targetX variables to the more appropriate doorX in
fn_check_access since they are only used if the target is a door.
