Where's the patch notes?

[Lancair]

This hotfix only changed what I noted above. No other changes were made.

Thanks for the reply Sapience. When I logged on this morning my retry timer was 15 hours, normally its 10, should I report a bug?

[Sapience]

Thanks for the reply Sapience. When I logged on this morning my retry timer was 15 hours, normally its 10, should I report a bug?

Yes, please.

[Leggilass]

Sapience I can see your point. However, if a group is in ToO and about to loot and lose it because of your tech crashing, that's not fair to those members. If yall are gonna test this I'd make some safeguards or goodie bags to accommodate for such an event to prevent justified hostility from the parties involved.

[Nakiami]

Thanks for the reply Sapience. When I logged on this morning my retry timer was 15 hours, normally its 10, should I report a bug?

I haven't done any league quests, but you probably just did it 5 hours earlier. The quests probably reset at 3AM server time like most dailies, so you'll get a different cooldown based on when you do them.

[Hurin]

Sapience I can see your point. However, if a group is in ToO and about to loot and lose it because of your tech crashing, that's not fair to those members. If yall are gonna test this I'd make some safeguards or goodie bags to accommodate for such an event to prevent justified hostility from the parties involved.

At some point, people are expected to "suck it up and deal." Exactly how much time and effort is Turbine supposed to expend soliciting complaints/claims, analyzing logs to verify those claims, generating the compensation, and distributing it? For those very few who for some reason can't just move on with their lives.

This is one of those things that falls in the "unfortunate but necessary" categories. The well-adjusted and adult population who don't go through life with a ledger in-hand making note of what they're owed and who is to blame understand this. . . and they're willing to deal with a potential/possible server crash in the name of progress against this ongoing/long-running issue. They'll just move on with their lives just as they would if their failed raid were caused by their MIN going link dead (should they call the MIN's ISP?) or a storm taking down the datacenter.

Stuff happens. And when stuff happens, people would be happier if they weren't staring so hard at their navel contemplating the "unfairness" of it all.

[Neumi]

Did this patch lengthen the repeat time for the Inn League beer quests?

Sometimes the display is faulty.

In my time zone the cooldown resets at 9am.

One day I finished the beer quests at 8:50am, the cooldown timer showed a cooldown of 17 hours! (that would be 2am, 0:00 greenwich time).

But half an hour later the timer was gone. It looks to me as if the engine was not able to create a shown reset time under an hour, so it chose the next "hot" time. But the reset took place at 9am as usual.

[Bradagast]

It says they will be here at downtime but i dont see them?

link me?

Bump! Seems like a pretty big patch...odd that there no clue about the content.

[Hurin]

Bump! Seems like a pretty big patch...odd that there no clue about the content.

There are no patch notes. See here (several posts up).

[Digero]

Sometimes the display is faulty.

In my time zone the cooldown resets at 9am.

One day I finished the beer quests at 8:50am, the cooldown timer showed a cooldown of 17 hours! (that would be 2am, 0:00 greenwich time).

But half an hour later the timer was gone. It looks to me as if the engine was not able to create a shown reset time under an hour, so it chose the next "hot" time. But the reset took place at 9am as usual.

That's a display bug for daily quests if you're not in the Eastern US time zone. When you complete a daily quest, it computes the time remaining assuming that the quest resets at 3AM in your local time, but in reality it resets at 3AM server time (EST/EDT). If you relog, you'll see the correct amount of time remaining.

I /bug'ed this several years ago.

[Chris2]

Looks like the default messaging got posted instead of the correct message that should not have included any mention of patch notes. There are none.

This patch is for some minor adjustments to the performance tech we added in the last patch. We identified some issues with it (issues that led to the Windfola crash last week) and believe we've resolved them. The tech, as before, will remain disabled until we're satisfied that everything else is stable (and wasn't accidentally impacted by these changes) before we select a single server and enable the tech again for testing.

As with the previous test, we won't be mentioning which world, when, or for how long the test will run to avoid any possibility of people reporting things inaccurately. We have full monitoring of this tech so we can see very easily what is and isn't happening.

Woah, Turbine goes to great lengths to avoid telling their customers what they're really doing to the game.

[Kerin_Eldar]

As with the previous test, we won't be mentioning which world, when, or for how long the test will run to avoid any possibility of people reporting things inaccurately. We have full monitoring of this tech so we can see very easily what is and isn't happening.

So paying customers are now enrolled into beta testing without their knowledge or being asked.

Nice.

[Neumi]

So paying customers are now enrolled into beta testing without their knowledge or being asked.

Nice.

The highlighted word is not correct, this has been the case for a while.
Remember the patch notes? "this should fix the sound problem".

Anyway, I don't care really if it won't reset the server or cause any other harm.

[0Pinger]

So this is TB's Party Trick, to those that like to use them, not nice is it when its you on the end of it.

[Nakiami]

Would you like them to fix the problem or not? Apparently, not.

[Leggilass]

At some point, people are expected to "suck it up and deal." Exactly how much time and effort is Turbine supposed to expend soliciting complaints/claims, analyzing logs to verify those claims, generating the compensation, and distributing it? For those very few who for some reason can't just move on with their lives.

This is one of those things that falls in the "unfortunate but necessary" categories. The well-adjusted and adult population who don't go through life with a ledger in-hand making note of what they're owed and who is to blame understand this. . . and they're willing to deal with a potential/possible server crash in the name of progress against this ongoing/long-running issue. They'll just move on with their lives just as they would if their failed raid were caused by their MIN going link dead (should they call the MIN's ISP?) or a storm taking down the datacenter.

Stuff happens. And when stuff happens, people would be happier if they weren't staring so hard at their navel contemplating the "unfairness" of it all.

The MIN going link dead is not something caused by Turbine (usually). Consider the need for experimentation (as this testing is necessary and it will be experimenting the stability of the tech client). When involved in such endeavors the participants are usually compensated for their time and troubles even if they are involved in something that they would normally have to pay to do. What would be so horrible about compensating the members of a particular server for their time and trouble? Stuff happens, true. If stuff happens and I cause it, I have consequences. Why should Turbine be any different?

[Ailedra]

Woah, Turbine goes to great lengths to avoid telling their customers what they're really doing to the game.

*blink*

Please actually read the thread (and check the link upthread) before jumping to (silly) conclusions.

[Lancair]

Yes, please.

Hi Sapience,

I finished the run this morning and looks like it is not a bug, they did up the time to 19 hours:

It use to be 10 hours

[Hurin]

The MIN going link dead is not something caused by Turbine (usually). Consider the need for experimentation (as this testing is necessary and it will be experimenting the stability of the tech client). When involved in such endeavors the participants are usually compensated for their time and troubles even if they are involved in something that they would normally have to pay to do. What would be so horrible about compensating the members of a particular server for their time and trouble? Stuff happens, true. If stuff happens and I cause it, I have consequences. Why should Turbine be any different?

By many accounts, people are failing raids regularly because of the issue this new tech is supposed to fix. Yet now, because people might fail a raid because of potential side-effects of the fix intended to stop people from failing raids, you want compensation if someone fails a raid. How does that make any sense? People are failing raids right now because this fix isn't implemented yet. But they're supposed to worry about the possibility that another raid might fail due to the process by which they fix the cause of so many failed raids? Do you want this fixed or not? How many disincentives to getting this issue fixed quickly do you want to put in Turbine's path?

But, fine. If something happens to you due to this issue, you can be that guy who screams, and whines, and moans, and generally makes an *** of yourself until Turbine gives you something to go away.

You seem to have no problem being that person. I do. So I seldom choose to be that person.

Some people have a grasp of the complexity of what they're dealing with here and see the necessity of how it's being handled in this instance to test its functionality and effectiveness properly. So we would feel strange asking for compensation for something that is necessary to achieve a fix. Others, however, just see an opportunity to mark their ledger and ask for some compensation. Or (in the case of others) carry on their long, twilight struggle against a game company.

Again, if you have no problem being that person, carry on. Lots of people don't. I personally find it bad form and more than a little unseemly.

--H

[Harla]

The MIN going link dead is not something caused by Turbine (usually). Consider the need for experimentation (as this testing is necessary and it will be experimenting the stability of the tech client). When involved in such endeavors the participants are usually compensated for their time and troubles even if they are involved in something that they would normally have to pay to do. What would be so horrible about compensating the members of a particular server for their time and trouble? Stuff happens, true. If stuff happens and I cause it, I have consequences. Why should Turbine be any different?

This is why, in a nut shell:

Suppose you are a gardener, and you generally try to take care of everything in your garden; in amongst your maintaing jobs, you sometimes have to kill pests or other creatures that can't remain where they are as you tidy. You're good person, and a bit of a naturalist to boot, so, when you can you prefer to take thirty seconds to pause and observe due respect to any poor creature you end up having to kill (or killing accidentally), while you garden, even the snails and worms.

Now, one day, you have an encroaching ant colony that is taking over a corner of your garden and starting to cause severe problems for everything around it... the only reasonable solution is to swiftly evict the ant-colony completely. You do this. Are you then, practically speaking, going to stop and take 30 seconds to observe due respect for EVERY SINGLE ant that died?

No, you aren't, especailly when you can't tell whether a given ant carcas is actually one that you killed, or if it was one that died at roughly the same time for completely mundane reasons. Forget not being practical, it borders on impossible...

That is why Turbine is not going to compensate you if your group wipes in ToO during this fix, and that is why it is rather notably foolish to expect them to.

-Harla