Now to see what's new/changed...
Hmm.. maybe false alarm, I can't find anything yet...
Well, it is taking longer to load. So at least there's that... :P
Edit: Paragon multiclass level 19 power bug is still there.
Edit 2: Power and Feat choices seem to be faster though. A lot faster...
1. Wizard power cards are still randomly arranged making it difficult to find the spell you're looking for during play.
2. The inventory screen still cuts off the names of equipped items, only shows something like 20 items total, and doesn't show the quantity of anything you own.
3. The feats/racial features section still has minimalist text descriptions of things, if anything at all.
4. It continues to show a feat that I retrained away (though, it does at least show the new feat, so I guess that's a draw?).
5. Power cards offer no ability to select which implement(s)/weapon(s) you want to use with a particular power.
6. Humans are unable to select their bonus language.
7. Buying/choosing equipment/magic items/rituals/etc. is still far more difficult than it should be because of the way items are buried under layers of category selections. Searching should always move from the general to the specific, not the other way around.
I don't know where to report these bugs. I think someone is compiling a list somewhere, but I don't think they work for the company do they?
While waiting for Trevor to post the official announcement, I can tell you that this is only a crash fix/stability release.
Thanks Paolo, forum goers are quicker than official releases.
So will look forward to what more news Trevor can give us.
These are the best programmers ever!
Stability issues are most likely caused by bugs. Especially those that require an update to fix. Also I'm rolling my eyes so hard at the rest of your post.
yay.
A month to get the buggy crapload to just be stable! No bug fixes.
These are the best programmers ever!
Much as I don't like the way in which you express yourself sometimes, I agree entirely with the sentiment. After even a month where one week was a writeoff due to snow and thanksgiving... so after three weeks... THREE WEEKS of presumably at least one full-time programmer working on this, all we have is a stability fix for the crashes which have actually seemed pretty stable since the first couple of days.
I hoped for more. I expected no less.
Perhaps they are testing other changes as we speak and are being super cautious about...
Ah who am I kidding? They're fixing the copyright date.
CB freezes.
From this I deduce conclusively that they did NOT fix all the crash bugs that they know about. Because they've been informed of that bug for some time, and it still crashes the ap.
I just tried to add a Tome of Replenishing Flame to a wizard.
CB freezes.
From this I deduce conclusively that they did NOT fix all the crash bugs that they know about. Because they've been informed of that bug for some time, and it still crashes the ap.
Minor quibble. If your browser doesn't close it's not a crash it's a "hang". Based on that I'd call that a client side bug. Since what they fixed is server side crashes and stability you can now arrive at that crash (hang?) faster and more reliably.
Thanks
Where are the druid, ranger, pally and warlock new build presented in the Forgotten Kingdom Essentials ? It's not supposed to be in the new CB patch ?
Thanks
Last I recall, they said they'd like to get those in before the holidays, but no promises.
Where are the druid, ranger, pally and warlock new build presented in the Forgotten Kingdom Essentials ? It's not supposed to be in the new CB patch ?
Thanks
Again, today's was just a stability patch.
Where are the druid, ranger, pally and warlock new build presented in the Forgotten Kingdom Essentials ? It's not supposed to be in the new CB patch ?
Thanks
Again, today's was just a stability patch.
And to state this once again the version number has nothing to do with the data set within the OCB. It is the version of the silverlight application they are using.
I believe Paolo was the one to inform us of this before.
I just tried to add a Tome of Replenishing Flame to a wizard.
CB freezes.
From this I deduce conclusively that they did NOT fix all the crash bugs that they know about. Because they've been informed of that bug for some time, and it still crashes the ap.
Minor quibble. If your browser doesn't close it's not a crash it's a "hang". Based on that I'd call that a client side bug. Since what they fixed is server side crashes and stability you can now arrive at that crash (hang?) faster and more reliably.
That is so going in my sig!
I just tried to add a Tome of Replenishing Flame to a wizard.
CB freezes.
From this I deduce conclusively that they did NOT fix all the crash bugs that they know about. Because they've been informed of that bug for some time, and it still crashes the ap.
Minor quibble. If your browser doesn't close it's not a crash it's a "hang". Based on that I'd call that a client side bug. Since what they fixed is server side crashes and stability you can now arrive at that crash (hang?) faster and more reliably.
That is so going in my sig!
So glad I could amuse you.
I just tried to add a Tome of Replenishing Flame to a wizard.
CB freezes.
From this I deduce conclusively that they did NOT fix all the crash bugs that they know about. Because they've been informed of that bug for some time, and it still crashes the ap.
I'm not sure they said they fixed ALL THE ISSUES that could concievably cause the program to crash. Just a minor quibble that has nothing to do with the semantics involved in the word "crash"
I just tried to add a Tome of Replenishing Flame to a wizard.
CB freezes.
From this I deduce conclusively that they did NOT fix all the crash bugs that they know about. Because they've been informed of that bug for some time, and it still crashes the ap.
I'm not sure they said they fixed ALL THE ISSUES that could concievably cause the program to crash. Just a minor quibble that has nothing to do with the semantics involved in the word "crash"
Oh, they probably never said they'd fixed them all. But then they never told us anything useful that I've seen about which ones they fixed.
They STILL haven't updated the Release Notes, FAQ, or Known Issues. And they HAVE issued a new patch, so one or more of those should be updated. (They even call the Release Notes "Patch Notes" in the link from the CB page. New patch, new patch notes, right? Well, wrong actually, I guess we get the old patch notes with the new patch, I'm sure that's useful to someone.)
Given that the bug has been reported (both here and as a bug report), and the bug report was marked as "solved" about two weeks ago (which surely means at the minimum that it was added to their internal list of issues), and given that they haven't added it to the public known issues or the FAQ at a time when ANYONE would expect those to have been updated, it MUST mean that this bug has been fixed! Especially when stability was the whole point of the update.
The problem isn't that they haven't fixed this. It's that the only way I KNOW whether they've fixed it or not is to open the code and try it. Because they don't tell anyone what they're doing.
"Stability bugs?" Which bugs got fixed? Am I and every other user supposed to individually retry everything that ever made it crash or hang and see which ones still do? And should we all resubmit our bug reports, or is there some way to know what they've done?
In any case, what's the point of having such documents and of requesting bug reports if you don't update the documents to reflect the actual known bugs? Hence we can again conclude that this isn't actually a known bug, which must mean it's now been fixed. Except that it hasn't been fixed.
This bug can make it impossible to upload a perfectly legal, completely non-houseruled character from the old builder to the new. And it's nearly impossible to identify WHY the upload fails (you have to realize you need to remove the tome and do so in the clasic builder, and you need to do this without anything telling you that the problem is the tome).
So this is the sort of issue which URGENTLY NEEDS to be in the FAQ. Yet it's not. So it must have been fixed, right? Surely you're not suggesting that Wizards would release a stability patch and not update their documentation to indicate significant remaining stability issues which users need to be aware of to use their product?
I can live with the buggy product, new releases are buggy. I can live with the odd update schedule. I can even live with the last MB update having broken the product and with them never planning to fix it (I'm not happy, but I'm not cancelling my DDI membership and I haven't yet asked for a refund for any of this). But I find the lack of updating to their documentation inexcusable. I thought OUR products that I work on in my day job were badly documented. We need to run training seminars so users can figure out how to use them. But they'd fire us and get someone else if our documentation was this bad. You make a new release, you update SOMETHING in the documentation. You ask for bug reports and collect God knows how many in a month and issue a patch, you also update your FAQ, you do know that FAQ means "frequently asked questions" and it should thus reflect the questions actual users are actually asking.
Where are the druid, ranger, pally and warlock new build presented in the Forgotten Kingdom Essentials ? It's not supposed to be in the new CB patch ?
Thanks
This is what is irritating me the most. I have a Pally for the Encounters game and I cannot put it on the CB. I just re-upped my subscription, but now I am feeling pretty shakey.
I have worked in the Video Game industry for 5 years (EA and Akklaim), and I know how things can go. One thing both companies that I worked for did was try and get resolution to issues by patching quickly. Granted it might take them several tries to get it right, but at least the fan knew they were trying to do something. So far WotC is not attempting to make that effort and you can see it in their fan base.
Hasbro really needs to look at WotC and its fans differently, we are not a community of people who are buying silly plastic toys (well to some degree we are), we are a community with lots of disposible income (hell I drop about 40.00 a week on gaming materials for D&D and other game I play), and if they piss those with the money off, they are going to loose lots of revenue.
Where are the druid, ranger, pally and warlock new build presented in the Forgotten Kingdom Essentials ? It's not supposed to be in the new CB patch ?
Thanks
This is what is irritating me the most. I have a Pally for the Encounters game and I cannot put it on the CB. I just re-upped my subscription, but now I am feeling pretty shakey.
I have worked in the Video Game industry for 5 years (EA and Akklaim), and I know how things can go. One thing both companies that I worked for did was try and get resolution to issues by patching quickly. Granted it might take them several tries to get it right, but at least the fan knew they were trying to do something. So far WotC is not attempting to make that effort and you can see it in their fan base.
Hasbro really needs to look at WotC and its fans differently, we are not a community of people who are buying silly plastic toys (well to some degree we are), we are a community with lots of disposible income (hell I drop about 40.00 a week on gaming materials for D&D and other game I play), and if they piss those with the money off, they are going to loose lots of revenue.
I'd also like to add that you have to be reasonably intellegent to play D&D so deceptive tactics are just going to fail more often than not.
community.wizards.com/go/thread/view/758...