dustyhansen

@Mr01sam any thoughts on this?

Thank you

yes

we noticed this in console when it happened the last time: 06/23 01:56:20 | [Convoy] assets/prefabs/deployable/chinooklockedcrate/codelockedhackablecrate.prefab preset was not found in the config! does that help?

why would you make us change it to keep it the way it was? how do i expand the text to make it not crop? and the white outline shows sometimes in the kill feed when not in edit mode in fact the white boxes around all of the elements in the notification have showed a couple times as well in the kill feed and what about the console errors?

Please acknowledge or I will have to report the plugin as broken.

I tried opening a ticket with the XD Quest plugin developer, but he said it is an issue with your plugin. Here is what I posted: XD Quests has a config option in config called "Ignore bonus from skill tree plugin when mining". When we set this to 'false', skill tree yields are still not taken into consideration for the quest. We tried setting to 'true' as well and same result. We thought it was an issue with his plugin and how he is using the hook, but he says you changed something that broke it. Here is his reply: So are you able to address this hook issue?

Also, getting this in F1 console

we are not on the same page, sorry you are disabling clan sharing, so of course it won't share it what i am saying is that i need to have clan sharing enabled for keylocks, so i don't want to disable that feature. but i have the plugin set to ignore codelocks and it is still affecting them. if "use only keylock" is set to true, then why is it still sharing codelocks and setting the code? i don't know how else to explain it

Also, sometimes the notification has a white border and sometimes it doesn't now.

The new update is cutting off the killer and victim names in the notification.

This is not true though. If I disable them and they manually place a codelock, the clan is added to the lock and the code is added as well. I'm not trying to argue here, just want to make sure that you understand what I am stating.

ok, i hear what you are saying, but i strongly disagree. sometimes players don't want to share everything with their entire clan. i don't think that is an unreasonable or uncommon scenario. and what is the point of disabling key locks then? if they are still shared and coded, then why even have the option to turn them off?

thanks for the reply. i don't want to change this because i want clan sharing on keylocks to still work. my point is that disabling keylocks doesn't actually disable them as the plugin still sets a code and shares them even though we have them set to be ignored.

We found a hole at Sewer Branch that we had to patch. Just wanted to make you aware.

We have the following setting set to true: "Use only Key Lock. [true] to allow only Key Lock. [false] to allow both Key Lock and Code Lock. (Default: FALSE)": true, The intent was to be able to allow code locks for private use and key locks for clan use. However, even though that is set to true, when placing a code lock on a door, for example, UltimateLocker still sets the code and authorizes the clan to the lock. This is problematic because the code being set cannot be edited as code locks are disabled. They are able to set their own code since the lock places in the unlocked state. But the primary issue is that it still authorizes the clan.

thanks! didn't see that

We noticed that there is still some issue with keylocks (not sure about codelocks). With a keylock placed on the basement (and sync set to true) players were still able to enter the basement and in one case were unable to get out. They shouldn't have been able to enter at all.

@imthenewguy should I open a support request with you then?

That didn't work for me when I tried it. It was selectable without a picture and when I chose it the building was in regular stone.

Here is my config. Convoy (2).json

Could you possibly add glow worms as an option for spawning? assets/content/nature/glow_worms/glow_worms_sparse_flat.prefab assets/content/nature/glow_worms/glow_worms_dense_flat.prefab

So I followed the instructions and made my PVP zone flag Undestr true. However, one of our PVP zones is launch site and this prevents players from damaging bradley. Can another flag be used possibly?