Blistersteel formula

[Synnestry]

Server crashes can really complicate things

Indeed, say you had it planned that your steel would be ready 4 hours before work today, plenty of time! *CRASH* nvm, gotta go to work now ..

[Scilly_guy]

Steel is supposed to be hard, you are supposed to work in a group to make it easier. The one thing that does get in the way is unplanned down time. Hopefully this will be a thing of the past once expeditions launch and they become the test servers. But inevitably there will be SOME unplanned down time. I am sure it would be possible to have some things work on the system clock rather than the server clock. ie some timers still tick when the server is crashed, or rather they suddenly tick a lot when the server comes back up. In this scenario when the server restarts it checks all the steel and if the time it was due to be completed has passed it starts the timer for taking it out, this would be server side, so that the steel doesn't turn to dross while the server is down and you have no way to save it.

Whilst this does have its benefits there would still be situations where server down time would cause people to miss steel deadlines. For instance your window for playing is 18:00 to 21:00, you time the steel to finish at 18:30, but the server is down, it comes back up at 21:01, it checks your steel and as it was supposed to be completed at 18:30 it starts the cooling timer. You can't log back on until 07:30, 10:29 after the steel finished. I don't know what was so important that meant you couldn't sort your steel out over night, maybe you work night shifts?

[Dallane]

Steel is supposed to be hard, you are supposed to work in a group to make it easier. The one thing that does get in the way is unplanned down time. Hopefully this will be a thing of the past once expeditions launch and they become the test servers. But inevitably there will be SOME unplanned down time. I am sure it would be possible to have some things work on the system clock rather than the server clock. ie some timers still tick when the server is crashed, or rather they suddenly tick a lot when the server comes back up. In this scenario when the server restarts it checks all the steel and if the time it was due to be completed has passed it starts the timer for taking it out, this would be server side, so that the steel doesn't turn to dross while the server is down and you have no way to save it.

Whilst this does have its benefits there would still be situations where server down time would cause people to miss steel deadlines. For instance your window for playing is 18:00 to 21:00, you time the steel to finish at 18:30, but the server is down, it comes back up at 21:01, it checks your steel and as it was supposed to be completed at 18:30 it starts the cooling timer. You can't log back on until 07:30, 10:29 after the steel finished. I don't know what was so important that meant you couldn't sort your steel out over night, maybe you work night shifts?

I don't think that is possible at all.

[Scilly_guy]

The server should have access to the system clock, something along the lines of

Code: Select all

//when lighting a cermentation furnace/putting steel in a furnace
mtSteelFinish=System.nanoTime()+CSTEELTIME;

//when the server restarts
if(mtSteelFinish>=System.nanoTime())
{
  //start the server timer for steel being ruined
}

[Ailaa]

Steel is supposed to be hard, you are supposed to work in a group to make it easier. The one thing that does get in the way is unplanned down time. Hopefully this will be a thing of the past once expeditions launch and they become the test servers. But inevitably there will be SOME unplanned down time. I am sure it would be possible to have some things work on the system clock rather than the server clock. ie some timers still tick when the server is crashed, or rather they suddenly tick a lot when the server comes back up. In this scenario when the server restarts it checks all the steel and if the time it was due to be completed has passed it starts the timer for taking it out, this would be server side, so that the steel doesn't turn to dross while the server is down and you have no way to save it.

Whilst this does have its benefits there would still be situations where server down time would cause people to miss steel deadlines. For instance your window for playing is 18:00 to 21:00, you time the steel to finish at 18:30, but the server is down, it comes back up at 21:01, it checks your steel and as it was supposed to be completed at 18:30 it starts the cooling timer. You can't log back on until 07:30, 10:29 after the steel finished. I don't know what was so important that meant you couldn't sort your steel out over night, maybe you work night shifts?

Well i personally travel alot, so i don't always have access to the game. But sure, there can also be people working night time. The point is though that the formula implemented to the creation of blistersteel is relaying on people scheduling when they can be online, 7 days ahead. And things can happen! Maybe someone gets sick and can't login, or a sudden travel, or working overtime, or forgetting, or whatever. The point is that the game should not punish you for not logging in, that is not a good game mechanic. Sure you can work in groups, but why should someone be punished for playing as he or she wants too?

[Scilly_guy]

The point of some mechanics is to encourage playing as part of a team. If you are unable to make steel/wrought iron/fine leather, whatever, you might be better off trading for it. Steel is a key example of where team work is really useful even if its not essential.

[Ailaa]

The point of some mechanics is to encourage playing as part of a team. If you are unable to make steel/wrought iron/fine leather, whatever, you might be better off trading for it. Steel is a key example of where team work is really useful even if its not essential.

Sure, life is easier if you are in a group. But everything in this game you can do alone. Hunting, making a town, making a brick wall, steel, wrought iron etc. It just takes hard work and dedication. Steel also takes dedication, i collect bones, leather, wrought iron, etc too make them. Taking alot of time. The only problem is one factor i can not affect, that is time. I can try to match the time it takes to make blister with my workschedule. But due to server crash or other factors irl time becomes a problem. The game should not punish people for having a life, and it most certainly should not make you have to rely on other people for your hard work. I am sure there is a big player base that prefers to play alone. Why should we punish those people? Of course i will be more careful in the future, but should i really have to reschedule meetings or job appointments for a game? It's just bizzare.

And no i do not want to trade for blistersteel, i want too make my own, in fact everything in this game i want too try and work hard too achieve alone. That is how i play, and i understand the tough consequences. Those being less secure, harder to get things etc. But one consequence i do not like is a factor of time i can not affect.

[Ailaa]

Anyway, this is a subforum for suggestions, so my suggestion is

- Remove the formula considering when you remove the blistersteel when it is finished.

or

- Make the formula so that you fail on one blistersteel after 8 hours, 2 after 16 hours, 3 after 24 hours and 4 after 32 hours.

[Scilly_guy]

I think they should look into the feasibility of my suggestion to remove the issues when the server goes down. I know that it might not be straight forward because of the way timers may current be handled, but that doesn't mean it couldn't be changed. It certainly IS possible for the server to know how much time has passed in the real world while it is offline. Sure, things can't happen when the server is down but they can happen when the server comes back up so that it appears they happened when they were scheduled to.

[ShadowTani]

I dunno, it should be possible if they used the servers clock to update the completion timers. And it would be ok as long as the pick up timers would only start their count from the time the server got back up, but what if the server went down again then? Would the pick up timers be put on hold then? It would not be very consistent. And it would be some programming with very little gain.