How do you people level up a character in the earlier levels if rushing isn't an option. My one leveled character is stuck in her Balrog Skin map so I need to make a new one for rushing other characters from scratch and it's been very slow. I'm 29 and hoping getting frozen orb and cold mastery next level helps speed things along.
Also what are the other rack targets I should look out for. My list was
Bone Knife (luckily a weapon rack in my balrog skin map also roles bone knifes ~30% of the time)
Shako
Winged Helm
Grim Helm
Thresher (for eth 4 socket weapons)
Bramble Mitts
Sharkskin Belt (Can't see wanting more than one of these)
The Grandfather (Colossus Blade) - 150% ED, but +175 life and 25% life and mana bonus
Baranar's Star (Devil Star) - 1.5 vitality per level, no elemental damage
Lightsabre (Elegant Blade) - 200% ED, 30% lightning absorb, interesting item type
Hellslayer (Decapitator) - +2 vitality per level, 150% ED, Indestructible, but the Enhanced max damage is less than in v1.09
don't forget a THUNDER MAUL! (In Nilly's temple). Having someone else try to get one will be good. Also, have you killed the ancients in the quest? Best way to level from the quest reward.
It just happens to work out like that in this case:
The formula will subtract (qlvl/2) from (clvl*66/100), but because (qlvl/2) is truncated to 0, it subtracts 0 from 60. Had an Amulet be qlvl 2, then you would need clvl93 for level 60 affixes.
Also, the final item level is not actually what directly determines the highest possible affix level:
If an Amulet was qlvl 2, then the highest possible affix level would be 59, while the final item level would still be 60.
Lastly, this is not the formula; just like in later patches, different formulas are used depending on the ratio between qlvl and (clvl*66/100), and whether or not the item has a magic level.
( It is a bug, by the way. The game wants/tries to do (clvl*66/100) + (ilvl*66/100), but the rune causes the second calculation to bug out and it ends up setting the value to 0, so this part always ends up as (clvl*66/100) + 0. Real shame that such a tiny mistake robbed us from truly incredible 1.07 crafts. :< )
What are the 1.07 thundermaul stats? Haven't found anything while searching. Any who could give me an additional rundown for the items to check for in 1.07 will be highly appreciated! Very curious about this stuff
What are the 1.07 thundermaul stats? Haven't found anything while searching. Any who could give me an additional rundown for the items to check for in 1.07 will be highly appreciated! Very curious about this stuff
What are the 1.07 thundermaul stats? Haven't found anything while searching. Any who could give me an additional rundown for the items to check for in 1.07 will be highly appreciated! Very curious about this stuff
Just curious. Do you see Patch 1.07 as a patch to play? Or do you see it as a patch to get nifty gear to use in other patches. I'm the latter and will probably never touch the patch (except maybe to get more max damage charms) once I get all the key uniques in the quantities I desire.
In this thread here, 1.07 mercenaries came up, and one thing in particular was act 5 mercenary damage as he has a one-handed sword equipped. I've taken a closer look, and thought I'd share:
If he uses Bash or Stun with a one-handed sword, his base damage is:
hireling_damage + item_damage + item_damage - 1
So, yes, his item damage gets doubled, and then 1 is subtracted.
However, when he does not use Bash or Stun, it actually gets even worse, because when he does not use these skills, then his damage from monstats.txt is added as well.
On Hell, this damage is a juicy 69-92, basically an extra weapon.
When using a two-handed sword, this doubling does not happen, and no monstats damage is added.
As for Bash and Stun, the reason they don't get any damage added from monstats is because these skills do "Attack 5", which (in monstats) deals 0-0 damage. His regular attack however does "Attack 4", so the game simply adds this damage from the monstats file.
(For your information, on Normal this damage is only 1-1, and on Nightmare it's is 37-49.)
His damage is then further increased by things like Strength and auras.
Bash unfortunately is bugged and does not add the flat +Damage that the skill description says it adds, because this +Damage is only added to the value that's used to calculate leech, and not to the actual attack damage that's dealt to the monster. This is also the case when the Barbarian uses this skill (sorry Bash enthusiasts!).
As for that hireling_damage, this is taken from hireling.txt, and assuming your merc was bought on Normal, this damage is calculated as:
(As usual, the remainder is truncated after the division.)
To give you an idea, let's say you bought a mercenary on Normal that's now level 80, and on Hell he does a regular attack using a Hydra Edge that has something like +100% Enhanced Damage:
The damage added up makes 229-413, then multiplied by strength makes 684-1234, and that's with a pretty mediocre sword.
Bash will have a lower base damage because of the lack of monstats damage, but this skill does have +% skill damage to make up for some of that loss. Stun lacks +%, so that deals the lowest damage.
Lastly, the mercenary screen is way off about his damage. I wouldn't even bother using it as a reference.
Well I used mine for cows where they absolutely need the HP boost. Really a general purpose merc, and things like oblivion knights would slowly kill it even with MDR armor + helm iirc.
I usually settled on skullders + GF sword + shako to grant an extra ~1k life iirc, with some mdr
@pharphis
As @zemaj implied, two-handed damage is calculated "normally". In the hireling's case, that means hireling_damage + item_damage.
I don't have a Grandfather myself unfortunately so I'm not sure if the damage per level stat is applied correctly. I remember reading about some bug related to two-handed weapons here at diabloii, but I can't remember what patch or what particular stat it was about. Something about a stat not being applied to two-handed weapon damage at all. (Maybe it was the +%Damage / level from Hellslayer, but not the stat from Grandfather that was broken?)
I can see the +life argument though since monsters are pretty relentless in 1.07, and mercenaries don't have a lot of hitpoints. If Holy Freeze was reliable/permanent I certainly would've picked that merc over the A5 one.
Oh, and I've edited my prior post, as I had actually forgotten to double the item damage in the example calculation. The damage looks a lot better now.
But for reference, this would be the calculation with a Colossus Blade with +150% Enhanced Damage in similar circumstances:
item_damage: 42-267
hireling_damage: 65-69
base strength: 199
The damage added up makes 107-336, then multiplied by strength makes 319-1004. So, still not too bad. And this hasn't even included the damage/level stat, so if that works properly, it's good damage. For final DPS there is of course the attack speed factor as well, but without the botty bnet economy you can't just give your merc a bunch of 40/15 jewels.
The bug you're referring to I THINK might be when you combine +dmg and %ED, or something like that. IIRC eth kelpie was severely nerfed for some reason related to this but maybe I'm totally misremembering what someone told me. Hopefully that sparks your memory or gives you an idea where to look.
ya mercs really need +life if they're going to actually tank at all, and the +life and +%life help quite a bit
@pharphis
Well I can confirm now that the +Max Damage per level on Grandfather does work, both when the sword is used one-handed as Barbarian, or two-handed as Barbarian or mercenary. The +%Max Damage per level on Hellslayer does not work however, and the +30-50 on Kelpie Snare also does not work. But this same stat is also found on Bloodletter, and on that weapon it does work, so it looks like it's a problem with two-handed specifically, and not so much the stat per say.
I was hoping the Kelpie Snare thing was just a display bug, but alas. At this point I feel like items like the The Grandfather are actually the exceptions when their stats are working.
And then some racking stuff. It was brought up on this page here, but it felt more appropriate to post this here for now. So far I've only checked the 1.07 weapon rack, but it's a start. (The idea is to find out the differences between 1.07 and 1.14 racks.)
OK, the weapon rack function will check every single weapon from the weapons.txt file, which in 1.07 has 305 entries. Every "eligible" item that is found is added to a list. If an item has spawnable set to 0, or quest set to anything other than 0, then the item does not get added to the list at all.
As expected, these are those items:
Code:
decoy dagger
Gidbinn
Wirt's Leg
Horadric Malus
Hellforge Hammer
Horadric Staff
Staff of the Kings
KhalimFlail
SuperKhalimFlail
If the weapon passed those checks, but its level is higher than (area_level - 1), it also is not added to the list.
If the weapon is not excluded at this point, then there's a small table that's accessed:
Code:
39 then x = 0
40 - 74 then x = 1
75 - 102 then x = 2
103 - 108 then x = 3
109 - 132 then x = 4
133 then x = 0
This evaluates (area_level - 1), and sets x to the appropriate value. So if (area_level - 1) is 87 like in Lower Kurast, then x = 2. Or if for example (area_level - 1) is 107, then x = 3. If you're wondering why this goes all the way up to 133+, well I'm just the messenger. Maybe they had great plans!
But what is this value? Well, every item has a rarity in weapons.txt. The chance that an item has for it to be added to the list is essentially (100/divisor)%, so if the divisor is 4, then there's a 25% chance it will be added to the list. If the divisor is 1 or below, the chance is 100%.
Now, this divisor is simply (rarity - x), while that rarity value is anywhere between 1 and 5, depending on the item, so some items inherently have a 100% chance to be added to the list, while the lowest possible chance is 20%.
To clarify the above, first x is subtracted from rarity, and then a random roll is done based on the result. If the random number generator returns 0, then the item is added to the list. This means that by the time you hit Lower Kurast, all items with a rarity of 3 and below have a 100% chance of being added to the list, as long as their level is not too high.
At this point, the function makes sure that if you're playing Classic, that the item is not expansion-only. For this purpose there's an expansion column in weapons.txt. Figured I'd mention it before someone gets ideas.
So, after all 305 entries from weapons.txt have been checked, a random roll is done. This random roll is simply the size of the list, so if there were 123 items added to the list, it'll be a random(123). As expected, the result simply points to the number on the list, so if the RNG returns 10, then whatever item was added 10th, that is the one that's picked.
Then, one last check is done, according to a bitfield, which is another column in weapons.txt. I suppose you could refer to this as "material", since it's used for more things, like Iron Golem. I think it's fair to say that anything "non-metal" is not allowed to drop.
So when the game checks this bitfield value of the item, and its material is non-metal, then the entire process starts over from the beginning. So it will create a new list from scratch, and finally does a random roll based on that new list. It will repeat this process until the random number generator finally picks a metal item.
The following items are considered non-metal, and when "picked" will cause the function to start over from the beginning:
Code:
Rancid Gas Potion
Oil Potion
Choking Gas Potion
Exploding Potion
Strangling Gas Potion
Fulminating Potion
Club
Spiked Club
Crystal Sword
Short Bow
Hunter's Bow
Long Bow
Composite Bow
Short Battle Bow
Long Battle Bow
Short War Bow
Long War Bow
Light Crossbow
Crossbow
Heavy Crossbow
Repeating Crossbow
Cudgel
Barbed Club
Dimensional Blade
Edge Bow
Razor Bow
Cedar Bow
Double Bow
Short Siege Bow
Long Siege Bow
Rune Bow
Gothic Bow
Arbalest
Siege Crossbow
Balista
Chu-Ko-Nu
Truncheon
Tyrant Club
Phase Blade
Spider Bow
Blade Bow
Shadow Bow
Great Bow
Diamond Bow
Crusader Bow
Ward Bow
Hydra Bow
Pellet Bow
Gorgon Crossbow
Colossus Crossbow
Demon Crossbow
Stag Bow
Reflex Bow
Ashwood Bow
Ceremonial Bow
Matriarchal Bow
Grand Matron Bow
Wand
Yew Wand
Bone Wand
Grim Wand
Short Staff
Long Staff
Gnarled Staff
Battle Staff
War Staff
Burnt Wand
Petrified Wand
Tomb Wand
Grave Wand
Jo Staff
Quarterstaff
Cedar Staff
Gothic Staff
Rune Staff
Polished Wand
Ghost Wand
Lich Wand
Unearthed Wand
Walking Stick
Stalagmite
Elder Staff
Shillelah
Archon Staff
Eagle Orb
Sacred Globe
Smoked Sphere
Clasped Orb
Dragon Stone
Glowing Orb
Crystalline Globe
Cloudy Sphere
Sparkling Ball
Swirling Crystal
Heavenly Stone
Eldritch Orb
Demon Heart
Vortex Orb
Dimensional Shard
Which leaves us to these items as contenders. I've included their rarity and level for completion's sake:
Well, that should be the entire thing already. As far as I could tell, there doesn't seem to be a flaw in the function that would allow an illegal item to drop, which is probably why we haven't seen them yet in 1.07. (Right?)
And I realize not all of this is news, but I figured it should be posted somewhere for proper comparison to 1.14.
Edit: And just my luck to spawn a top-tier LK layout when I'm testing stuff on Normal...
Oh I can assure you this is only one of many examples where they waste resources by looping stuff like this. It hurts to go through the code at times. In this case they could've even cheaply simplified it so that it just checks the next item on the list, and move down until one is finally valid. I assume that 1.14 is not this bad, but 1.00 - 1.07 has a ton of code like this. Cases like where it calculates all the damage and does all these random rolls and such, and only then it checks if the attack even hits at all, and if it doesn't hit, all those calculations for nothing. It's depressing.
Oh I can assure you this is only one of many examples where they waste resources by looping stuff like this. It hurts to go through the code at times. In this case they could've even cheaply simplified it so that it just checks the next item on the list, and move down until one is finally valid. I assume that 1.14 is not this bad, but 1.00 - 1.07 has a ton of code like this. Cases like where it calculates all the damage and does all these random rolls and such, and only then it checks if the attack even hits at all, and if it doesn't hit, all those calculations for nothing. It's depressing.
The damage looks a lot better now.
