fix: uptime in protocolstatus

[htc16]

Description

There is an uptime error in protocolstatus, as it does not load the time in the cache correctly, causing it to not update the time.

I added this variable within uptime, so that, instead of using the cache time, in specific cases it loads the system time, so it is possible to use this in other parts where uptime is a problem, just adding the true inside OTSYS_TIME().

This fixes a time overrun, where the server had been online for over 53 years. One other player and I had this problem, I don't know if other people did.

Behaviour

Actual

Do this and that doesn't happens

Expected

Do this and that happens

Fixes #issuenumber

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Server Version:
• Client:
• Operating System: Debian 12

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I checked the PR checks reports
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[Necromonde]

Fiz toda essas alterações e o uptime continuou o mesmo

[htc16]

Did you test it correctly? Did you delete the cache from the previous compiler?

[elsongabriel]

Did you test it correctly? Did you delete the cache from the previous compiler?

How can we test this?

[htc16]

Did you test it correctly? Did you delete the cache from the previous compiler?

How can we test this?

I believe this can occur using debian 12, which is my case, I'm not sure of the real cause of this, because the problem is limited to some people from what I could see.

[elsongabriel]

Did you test it correctly? Did you delete the cache from the previous compiler?

How can we test this?

I believe this can occur using debian 12, which is my case, I'm not sure of the real cause of this, because the problem is limited to some people from what I could see.

I'm checking here, and Myaac give me Uptime: 475597h 48m
I'll fix this return, with days and hours.

but, where can we check our uptime?

[htc16]

Did you test it correctly? Did you delete the cache from the previous compiler?

How can we test this?

I believe this can occur using debian 12, which is my case, I'm not sure of the real cause of this, because the problem is limited to some people from what I could see.

I'm checking here, and Myaac give me Uptime: 475597h 48m I'll fix this return, with days and hours.

but, where can we check our uptime?

From what I understand, the wrong return happens because the system for starting the server cannot even have a predefined time, and when it arrives at the moment that leaves the server online, it loads the 0 uptime that is stored in the cache when it starts. I believe that's it. The only change I made was a modification to the source so that the server gets the system time directly without accessing the cache when online.

[elsongabriel]

Did you test it correctly? Did you delete the cache from the previous compiler?

How can we test this?

I believe this can occur using debian 12, which is my case, I'm not sure of the real cause of this, because the problem is limited to some people from what I could see.

I'm checking here, and Myaac give me Uptime: 475597h 48m I'll fix this return, with days and hours.
but, where can we check our uptime?

From what I understand, the wrong return happens because the system for starting the server cannot even have a predefined time, and when it arrives at the moment that leaves the server online, it loads the 0 uptime that is stored in the cache when it starts. I believe that's it. The only change I made was a modification to the source so that the server gets the system time directly without accessing the cache when online.

ok nice.. I fixed myaac serverinfo page, to show like this:

[htc16]

Did you test it correctly? Did you delete the cache from the previous compiler?

How can we test this?

I believe this can occur using debian 12, which is my case, I'm not sure of the real cause of this, because the problem is limited to some people from what I could see.

I'm checking here, and Myaac give me Uptime: 475597h 48m I'll fix this return, with days and hours.
but, where can we check our uptime?

From what I understand, the wrong return happens because the system for starting the server cannot even have a predefined time, and when it arrives at the moment that leaves the server online, it loads the 0 uptime that is stored in the cache when it starts. I believe that's it. The only change I made was a modification to the source so that the server gets the system time directly without accessing the cache when online.

ok nice.. I fixed myaac serverinfo page, to show like this:

but the problem is also with otservlist and the server score starts to drop so much!

[github-actions]

This PR is stale because it has been open 45 days with no activity.