REDLINER Weapon Compare
Sort and inspect Castigate, Phoenix, and Siege using source-backed values and mobility tags from the TRELLOLINER snapshot.
How to choose between Castigate, Phoenix, and Siege
Start from the route you can actually play. Castigate is the cleanest learning weapon because its one-handed tag supports wallrun and augment use, and its magazine gives more attempts before a reset. Phoenix is the highest threat option when the player can aim projectile pressure, but the two-handed tag changes movement planning and the explosive risk makes parry decisions more severe. Siege sits closer to a commitment weapon: it wants short distance, accepts a slower draw, and asks the player to manage recoil and spacing rather than simply chasing damage text.
The comparison should be used with the calculator and parry trainer, not in isolation. If you choose a two-handed gun, open a movement route and remove wallrun assumptions. If you choose Phoenix, run the parry drill that covers explosive pressure. If you choose Castigate, practice routes that prove the one-handed advantage instead of standing still and trading shots.
Source Policy And Measurement Plan
REDLINER Wiki pages use three evidence layers: official Roblox metadata for game identity and controls, the TRELLOLINER snapshot for mechanics and weapon notes, and local SEO research for what players are actually searching. When a value is balance-sensitive, it is presented as source-checked snapshot data rather than a guaranteed live formula.
The success metric for this page is practical usefulness, not only pageviews. A healthy session should send readers into at least one related guide or tool, keep bounce rate lower than a thin code table, and help players complete a real task such as checking code status, choosing a weapon, setting controls, or planning a movement route.
Use the page in three passes. First, complete the visible tool or checklist without changing any advanced assumptions. Second, open one related guide from the sidebar or body links and compare the result against the source note. Third, test the recommendation in game and return to the source log if the live behavior no longer matches the snapshot. That workflow is the quality bar for REDLINER tools: they should reduce uncertainty, expose limitations, and point to the next useful action instead of trapping players on a single thin page.