Fix the inaccuracy used when lock on in Missile.

[dnqbob]

Fix regression from #18009

It should be just an oversight

[PunkPun]

Looks like it was done this way for every projectile on purpose 76dfda1

[dnqbob]

No, this PR is not related to change standalone inaccuracy to util, it is related to an oversight in 76dfda1.

			var inaccuracy = lockOn && info.LockOnInaccuracy.Length > -1 ? info.LockOnInaccuracy.Length : info.Inaccuracy.Length;

			if (inaccuracy > 0)
			{
				inaccuracy = Util.ApplyPercentageModifiers(inaccuracy, args.InaccuracyModifiers);

				var maxOffset = 0;
				switch (info.InaccuracyType)
				{
					case InaccuracyType.Maximum:
						maxOffset = inaccuracy * (targetPosition - pos).Length / args.Weapon.Range.Length;
						break;
					case InaccuracyType.PerCellIncrement:
						maxOffset = inaccuracy * (targetPosition - pos).Length / 1024;
						break;
					case InaccuracyType.Absolute:
						maxOffset = inaccuracy;
						break;
				}

			var inaccuracy = lockOn && info.LockOnInaccuracy.Length > -1 ? info.LockOnInaccuracy.Length : info.Inaccuracy.Length;

			var maxInaccuracyOffset = Util.GetProjectileInaccuracy(info.Inaccuracy.Length, info.InaccuracyType, args);
			offset = WVec.FromPDF(world.SharedRandom, 2) * maxInaccuracyOffset / 1024;
``

[dnqbob]

You can see in old code of 76dfda1,
Missile should use LockOnInaccuracy when lock on, and use Inaccuracy when it does not lock on, while the change in 76dfda1 make the missile all use Inaccuracy no matter it locks on or not. I think the author just simply make a mistake on this one.

[PunkPun]

Changelog