CCP_Explorer

And were you then able to submit again once the 24 hour timer expired? Please send us a bug report.

What’s the EBR number of your bug report?

Please note that bug reports and support requests are two different things. If you need help from Customer Support, please visit the Help Center and open a chat or send in a support request. If you are reporting a bug then they are collected in our defect tracking system for the Dev Team, where they will be processed, but we may or may not respond to individual bug reports.

Can you detail this a bit more, please?

Can you send us a bug report, please, with the details on these NPCs and/or sites; and reply back with the EBR number?

I’ve forwarded the feedback thread issue to the relevant people; there is something weird happening with the settings on that thread.

I’ve located the EBR you sent; we have already a few bug reports on issues that look very similar so we will be collecting them all.

I don’t think any events or sprees were active yesterday… (and are therefore not active today and won’t be active tomorrow) but I’m asking around.

Located, thanks.

It would be very helpful if you include the EBR numbers in your posts.

Please bug report everything that should have respawned or replenished, but didn’t.

Except the regular asteroid belts, we know about that issue and that doesn’t have to be bug-reported.

But we would like to know about all other content that players use regularly and that doesn’t behave today as expected.

They are not actual inventory items, but they are “Dungeon Distributions” as far as I know and this particular feature may be something that only runs on server startup. Please send us a bug report and reply back with the EBR number.

Yep, a known issue with the regular asteroid belts.

Currently the regular asteroid belts are actual real items in the inventory system that are replenished during downtime in a DB job while the inventory system is offline. Since the cluster didn’t go offline then the inventory system was still up-and-running and then the DB jobs could not run.

No; they will be replenished in tomorrow’s downtime.

Excellent!

Expected, the regular asteroid belts were not replenished.

Before #nodowntime becomes are regular pattern, these sort of issues would need to be resolved.

I’m not sure…

There are no changes to code or content today. We are setting up tests, disabling things that would run at tomorrow’s downtime (if there was one), and informing players and getting them engaged. The primary part of this experiment starts at 11 o’clock tomorrow.

EDIT: I checked with devs. The Caldari Union Day event ended today and there are no other time-limited events currently running. The daily login campaign is active.

There has been a fair amount of comments & questions in this thread on why we are looking at downtime; what’s the problem with a few minutes each day.

The first problem is that it interrupts primary play sessions for players in Asia and Oceania. Downtime at 11 o’clock EVE Time doesn’t affect Europe that much and doesn’t really affect the Americas at all. I covered this in detail in my 2019 dev blog on No Downtime Vol. 1 and the various options if downtime was not at 11 o’clock.

The second problem is that this is a larger impact than a few minutes. Shortly before downtime players start looking at ...

What Geo said – but to find out how all the different systems in EVE respond on this scale, then we are testing what happens.

If there are any daily things that you do or claim today, and then you can’t tomorrow; then please create a bug report and ping me here again with the EBR number.

To engage players to help us test; see e.g. https://twitter.com/KhapriceHeska/status/1435572675171192839