Weapons in The Lord of the Rings: War in the North™ - Legacy Edition should be compared inside the job of the hero using them. Eradan needs a dependable bow lane and a safe sword response, Andriel needs equipment that complements magic and survival, and Farin needs melee pressure he can deliver while holding the front. Use AppID 2523770 item text and behavior instead of importing fixed values from the retired original.
Compare function before rarity
Read the compatible hero, attribute requirement, displayed damage, bonuses, and socket state. Rarity can identify an item worth inspecting, but it does not guarantee a better result for the current build. A weapon that requires several off-plan attribute points may delay more useful growth, while a modest weapon with the right timing can keep a dangerous target from acting.
Equip the candidate on the intended hero and use a familiar encounter. Keep difficulty, companion setup, and skills unchanged. Count the meaningful actions needed to complete the weapon’s job rather than recording one unusually large hit. Also note damage received and resource spent during the sequence.
Retain the previous weapon until the test is complete. Inventory decisions made immediately after a dramatic drop are prone to missing requirements or a useful old bonus. Sell only after the replacement works through a checkpoint, town transition, and normal reload.
Evaluate Eradan’s bow and swords as one kit
The official role describes Eradan as precise with bows and swords. For a bow, compare target acquisition, practical firing rhythm, shots to stop a priority enemy, and the safety of the position required. A weapon that performs well only while Eradan stands exposed may be worse for a difficult cooperative room than a slightly weaker consistent bow.
Swords answer contact. Test whether the sequence lets Eradan finish a weakened enemy or create room without consuming the resource reserved for escape or ranged pressure. Do not judge the sword by whether it can turn the Ranger into Farin. Its purpose is to preserve control when distance collapses.
Match bonuses and elf-stones to the same job. If archers survive one action too long, improve the ranged sequence. If Eradan is interrupted while aiming, inspect movement, armor, and safety before adding another narrow offensive effect. The Eradan build connects these choices to skills and attributes.
Judge Andriel’s weapon through spell access
Andriel is the fellowship’s Loremaster, with official emphasis on healing and area effects. Her weapon should not be compared solely through ordinary attack output. Watch whether it supports the resource, defense, or attribute context that lets her perform the needed cast at the needed moment.
Run a mixed encounter and record whether healing arrives before a companion falls, whether area pressure interrupts clustered enemies, and whether Andriel can recover after being targeted. A weapon bonus that improves a secondary attack but leaves the essential spell unavailable may not be an upgrade for the current party.
Position remains part of the result. If the weapon comparison requires Andriel to stand where she is constantly interrupted, solve the lane and companion spacing before concluding that the item is weak. Save a functional previous option until the new setup has handled both routine groups and a longer encounter.
Test Farin’s melee choice under pressure
Farin’s official identity is a durable Champion with powerful melee combat. Compare weapons while he is actually holding close enemies, not against a target that cannot respond. Observe attack commitment, reach, ability to interrupt or finish, damage traded, and the time needed to block, evade, or turn toward a new threat.
A large number may hide a slow sequence that lets another enemy bypass him. Conversely, a quicker weapon may fail to create enough pressure and extend the fight until the party runs out of recovery. Choose the option that makes the front predictable for Eradan and Andriel.
Test against a group as well as an isolated durable target. The first reveals crowd control and turning safety; the second reveals sustained output and resource behavior. Avoid assigning a universal ranking when bonuses, requirements, skill investments, and drops differ among saves.
Decide when an attribute requirement is worth meeting
Count the points between the current attribute and the requirement. Identify what those points would have supported in the existing build and how many levels the detour requires. A near-term threshold for a clearly superior weapon can be reasonable; a distant threshold for an untested item can leave the hero weaker throughout a major part of the campaign.
Do not throw away the candidate immediately if the gap is modest. Store it, note the requirement, and test other upgrades before the next level. If a better weapon appears with a reachable requirement, revise the plan. Equipment should inform attributes without dictating every point.
After meeting a threshold, verify that the weapon is equipped and that its real behavior solves the intended problem. If not, return to the previous weapon and let future points serve the build’s main purpose. Avoid changing save files or forcing an unsupported respec because one drop disappointed.
Socket only after the base weapon earns its place
Use the weapon without a valuable elf-stone first. If its range, timing, and requirement already fit the job, name the remaining limit. Then select a socket effect that addresses that limit. This prevents an expensive stone from making a poor base weapon look temporarily attractive.
Inspect current Legacy Edition menus for whether a stone can be removed, overwritten, or recovered. Do not rely on a retired-AppID procedure for an action that may consume an item. When uncertain, experiment with a disposable effect or postpone the socket until a durable weapon appears.
Keep comparisons clean: one weapon or one stone at a time. Record the test encounter and result in a short note. The aim is a reliable party tool, not a speculative spreadsheet assembled from incompatible versions.