Malkizid

HI Fruster, Thanks for the info, I will try this out as soon as I can. I will get a chance a bit later today.

Hi Fruster, Do you have any idea why this might be happening to some DungeonBases? I haven't modified any of the designs and am using the default designs included with the plugin. Sometimes this error occurs near server save and the base doesnt appear or doesnt remove properly. It was not happening previously, this also does not happen often, only sometimes. I know that is not very helpful info but I have been unable to determine the cause. I hope you might have a suggestion for me to check, Thanks in advance. - Manky (21:46:46) | [Dungeon Bases] No hatch found, or both hatches not found (21:46:46) | [Dungeon Bases] The event will not start (21:46:46) | Calling kill - but already IsDestroyed!? door.hinged.bunker_hatch (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? #dung#undestr# (21:46:46) | Calling kill - but already IsDestroyed!? Cobalt Researcher (21:46:46) | Calling kill - but already IsDestroyed!? Cobalt Security (21:46:46) | Calling kill - but already IsDestroyed!? Cobalt Researcher

Forwarding the end of our conversation here as per our conversation in the inbox. "I've resolved this, I'm pretty sure it was an inconsistency with the machine time and the actual server config time. It seems to be working, now I can get past day1 day 2 etc. I wasn't aware how the plugin used the server time. Sorry for the annoyance and thank you for the support I had to wait in realtime as I didn't have a test server option to mess with the config and increase the speed of reward times for testing, outside of our live server."

Thanks for the reply Mevent, - config yes no problem ( btut it will be the config version from 2.1.9) - data file with kits settings, will send you no problem - its out of the question to ask my players to record videos and guess what kits work and what dont, sorry. all that would be seen is a naked player looking at the kit menu recieving an error message, sying "no space can't redeem kit" I will direct message you through your inbox with the files. Thanks in advance, Kind regards, Manky

I had to revert to version 2.1.9 again because of the problems made with the released updates 2.2.2 and 2.2.3 I can confirm zero issues with players redeeming Kits when rolling abck to v 2.1.9 again.

Some players still can't redeem our kits, they get the not enough space warning. Even when the player is not wearing any items. The Kit that failed has 4 empty slots in the invetory Full player clothes items and full player toolbar items. I can redeem it, however some players can not. Its not a permissions issue. Perhaps its a problem with kits that had the backpack slot equipped before the update. As all worked in version 2.1.9 none in 2.2.2 and now only some work in 2.2.3 All of the kits I have available for players, have something equipped in the backpack slot and were made in version 2.1.8 or earlier Should I edit the kits and remove the items in the backpack slot? I'm guessing here as I have had no luck yet in testing, as we dont have a test server right now. Thanks in advance for any help on this issue.

Hi Mevent Team I've been having problems with this for months. The timer only displys for the Day 1 Reward, it can be taken. The Day 2 reward never unlocks. Its never possible for any of our players to get past the Day 1 Reward. Configuration is essenitally unchanged, I have changed some reward items, to test but no luck. IS there something I should look for, I can not figure out why its not functioning. My server restarts every day at 05:30 am the DailyRewards configuration timezone and restart time is configured the same as my server time. Do you have any suggestions as to what I should look for to fix this? Is there an alternative solution maybe? Thanks in advance.

Yes the issues are fixed, thank you Mevent Team

Hi, did you manually revert all your data and configs for version 2.1.9

Same, nobody can redeem any kits on our server, no matter how many items are in it! Please help

Thank you, Yes the newly uploaded .zip contained the correct version v1.2.1

Hi, Any info as to why the latest version is still unavailable to download? I can only acquire version 1.2.0 version 1.2.1 still will not download. Thanks in advance, regards, Manky

Hi Mevent, thanks for the reply. Ok as long as you are aware. I was suprised as 4 hours since upload time seems like an aweful long time for a trivial caching problem. I guess Codefling is having some issues.

The file version downloading from Codefling is still 1.2.0 from March, please check the upload again as it is not v.1.2.1 available, thanks in advance. Kind regards, Manky

The internal version number is incorrect

Hii Mercury, The English plugin version is not correctly downloading 1.15.14 - the version I get is 1.15.13 - can you check the upload again please ?

Same, as when a server save is triggered - it triggers many of our other plugins to force a save state and lags everything too, outside of our predefined server save interval our config, causing too many overlapping save states. I've had to remove DungeonBases for now. To add a "save state" disabling option to the configuration would be very appreciated!

Thank you Fruster, yes it is absolutely important for Server owners to not have plugins forcefully trigger saves when out of synchronisation with the server save state. Or to at least be made aware of it - I do understand its important to ensure your plugin works and no data is lost but this method is not ideal. This should be the responisiblity of the server owner to configure. Thank you for your understanding. I am willing to take the risk to use the plugin if we can configure the save states. but I cant use the plugin when we end up with 3+ save states on top of eachother. There are 4 save states by the plugin, not only on base spawn. On plugin load, on base event start on base unload on event end is too much