Jump to content

Crate timer broken

Closed 1.1.7

MrLiquid
MrLiquid

Posted

Hello, Thank you for your fine work however;

 

After loading, timers were at 140 minutes, I change the config to 5 mins, now the crates unlock without any timer at all.. suggestions?

 "Crates timer(in seconds)": 300,

Fruster

Posted

Hey, i will check it soon

Fruster

Posted

Changed Status from Pending to Work in Progress

Fruster

Posted

I can't find the problem. Please describe in more detail and show your config file

MrLiquid

Posted

When the cargo plane drops the load. "event starts"... I have the crates timers set to 5 minutes (300 seconds), once I click to "Hack" the crate.. the timer shows 5 minutes for a second, then immediately jumps to 0.00, thus not counting down from 5 minutes.

 

Attached is my config file.

 

Keep in mind, prior to your recent update, I had no problems with anything. 

AirfieldEvent.json

Fruster

Posted

Please set the default timer to 900 seconds first and check.  it is also possible that third-party plugins affect this, try checking without them

MrLiquid

Posted

Ive never had any problems with your plugin until this latest update. you do fine work

MrLiquid

Posted

I've adjust as you asked, I'm just waiting for the event to begin so I can see how it responds.

MrLiquid

Posted

the change of setting to 900 has them now counting down from 5 mins, strangely that worked!. thank you

Fruster

Posted

this is strange, it should be 15 minutes, as it was by default. Perhaps you didn't reload the plugin after changing the config?

MrLiquid

Posted

I certainly did reload it, I do have server config set a timer limit on all hackable crates to 300. 

 

hackablelockedcrate.requiredhackseconds 300

Fruster

Posted

well, if the problem is solved, then with your permission, I will close the ticket

MrLiquid

Posted

seems to be working fine, while it is set at 900 seconds, it is still counting down from 300 seconds (5 min) if you are happy with that, then yes close the ticket

Fruster

Posted

it shouldn't be like this, is there any way you can test on a clean server without other plugins?

MrLiquid

Posted

here is the latest error

 

[AirfieldEvent] Event started
[AirfieldEvent] Next event will start in 3900 seconds
Failed to run a 3.00 timer in 'AirfieldEvent v1.1.7' (ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index)
at System.ThrowHelper.ThrowArgumentOutOfRangeException (System.ExceptionArgument argument, System.ExceptionResource resource) [0x00029] in <fb001e01371b4adca20013e0ac763896>:0
at System.ThrowHelper.ThrowArgumentOutOfRangeException () [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
at Oxide.Plugins.AirfieldEvent.NpcAI (BaseEntity npc) [0x00324] in <7d0869e36fe44c9ca9144cd761af5708>:0
at Oxide.Plugins.AirfieldEvent+<SpawnDrop>c__AnonStorey2.<>m__1 () [0x00010] in <7d0869e36fe44c9ca9144cd761af5708>:0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <d5f57e12edfe4fa0b5c5dbdd9b51eff8>:0

Fruster

Posted

This timer error is not related to the crate timer, it is related to the npc, is there any way you can test on a clean server without other plugins? I need to understand what exactly causes the error

Fruster

Posted

did you manage to solve the problem?

MrLiquid

Posted

reloaded the plugin, no errors reported yet

MrLiquid

Posted

I run a working server, there is no way I can run a clean server without interrupting my paying players sorry

Fruster

Posted

ok, then with your permission, I close the ticket?

MrLiquid

Posted

sure, if you are satisfied the problem is resolved 😆

Fruster

Posted

Changed Status from Work in Progress to Closed

1.5m

Downloads

Total number of downloads.

7.3k

Customers

Total customers served.

109.9k

Files Sold

Total number of files sold.

2.2m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.