CompTargetable.OrderForceTarget causes desync.

[Sakura-TA]

This occurs when trying to use item with CompTargetable. The comp cached Pawn caster when select use option and uses it in OrderForceTarget, which synced by MP.
e.g. 'amplifier' from Mod 'Infused'.
It seems Rimworld nolonger use this comp though.

Register SyncWorker for CompTargetable to sync caster can fix this, but I've got no idea where to put the codes, since MP project seems not as active as MPcompat, so I made a issue here. xd

Related RW codes

public override bool SelectedUseOption(Pawn p)
		{
			if (this.PlayerChoosesTarget)
			{
				this.caster = p;     //caster setted here
				Find.Targeter.BeginTargeting(this, null, true, null, null, true);
				return true;
			}
			this.selectedTarget = null;
			return false;
		}
		public void OrderForceTarget(LocalTargetInfo target)
		{
			this.selectedTarget = target.Thing;
			CompUsable compUsable;
			if (this.parent.TryGetComp(out compUsable))
			{
				compUsable.TryStartUseJob(this.caster, target, compUsable.Props.ignoreOtherReservations);
			}
			this.caster = null;
		}

[SokyranTheDragon]

This is causing desyncs with (Ghoul) Resurrector Mech Serums. A sync worker may fix the issue. Probably. We'd need to check how the fields are handled to make sure there's no issues where we replace a correct field value with an incorrect one.

[Sakura-TA]

afaik, this caster field was only for CompTargeter.OrderForceTarget to figure out which pawn calls SelectedUseOption. If caster is synced around OrderForceTarget, would cause issues when 1 player done selection given the jobs and the other player called SelectedUseOption on same thing but on ticks behind, at this point the other player would got his caster replaced. sync SelectedUseOption here would fix this and no more sync worker needed. :P