Posted to UO Herald by Jeremy Dalberg




November 2, 2007

The Stratics Smith Forum FAQ says, "The deed you get at and after 70.0 Real is completely random, though GM smith's have a slightly higher chance of getting a better deed." Can someone quantify the "slightly higher chance?"

Wilki says,

"GM and above gets a 20% better chance of receiving a colored BOD, and roughly a 50% better chance to get an exceptional BOD."

--

"Why don't GM and higher Smiths get large iron armour bods?"

As near as we can tell, they can and should. If anyone has collected substantial data to the contrary, please send in feedback - looking at the code, there's no reason why you shouldn't that we can see, but when enough of y'all believe something, it sure makes me nervous.

--

"How is Reflect Physical Damage actually calculated?"

Wilki says,

"Reflect Physical Damage reflects only a percentage of the actual physical damage you’ve taken after your physical resist is taken into account. The amount reflected does not lower the amount of damage you take."

So, say a monster takes a swing at you, and the hit would do 100 physical damage. But you have a 50 physical resist suit on, so only 50 damage gets through. You're also wearing items that add to 10% Reflect Physical Damage. What would happen is you take 50 damage and the monster that hit you would take 5 damage.

--

"Why does this "Choose you chat handle" window keep popping up over and over?"

It appears to be an issue that occurs when two identically-named characters are logged into a shard at the same time. (Why this only started happening recently, I'm not precisely sure yet.) Usually I try not to mention stuff like this in the FoF until I have an idea of when the fix will go in, but I wanted to reassure everyone that we're aware of it, annoyed by it, and working on it, and I'll keep you posted as I get more details.

--

"Why haven't we seen much/any rubble and destruction in Magincia yet?"

The event is still in the early phases - the rubble won't be created at all until a later stage. We're also working on a couple of fixes that will make the spawn a little more consistent and scale better based on player activity - you can check out some of these changes on the Halloween 2007 test shard over the weekend.

--

Have a great weekend, everyone - try not to catch on fire!

- Jeremy

Good reading- thanks Tabbitha

AAHAhahahhahaa...

oh man...

But seriously though, I'm not challenging Wilki in any way, nor do I have any statistics to prove the system isn't working as expected. I can only speak from experience as to why I'm not collecting BODs. Worst, system, ever.

I don't think this is right. None of our characters that have that annoying gump pop up have regular names. I always check to make sure that they're the only ones with that name and last name in the shard.

Nay it's not right, I had that gump come up several times when I logged into a newb account with a character name of "Adam_UOF".
There aren't any on the shard I logged onto.
*wonders how many other "annoyances" will popup only on the 2D client in the months to come*

*nods*

Such an implyer

*deletes "Adam_UOF" character*

Yet another little tidbit as to why this invasion is just another thing going in the wrong direction for UO.

So, from the description, reflect physical is next to useless. NIIIIICE. Wonder why they have such a passion for it though?
Not sure, cause I avoid this property like the plague, but doesn't the dealth damage also get reduced by the original attacker's physical resists? I played around with it when it first came out, and it looked like it did.

Necromancers with -15 Physical resist + 100% Reflect Physical Damage + Blood Oath and more HP than their attacker = Win!

There is an exception..... remember that certain non "moditor" spelling tomatoe sucking vampire who couldn't kill me...hehehe

i think reflect physical go up to 105 but if you could incorate that in your suit would'nt be half bad

oh thanks for the post tab

This has been broken for years...since way back when I collected bod's--and that's been a LONG time. Now, this was an acknowledged problem, and I suspect that whichever devs KNEW about this problem quit sometime before living memory.