I can confirm that I am experiencing this issue on my end aswell.

There are some indirect approaches via character command handler to force weapon fire:

//------------------------------------------------------------------------------------------------
modded class SCR_CharacterCommandHandlerComponent : CharacterCommandHandlerComponent
{
	protected bool m_bACE_ForceWeaponFire = false;
	
	//------------------------------------------------------------------------------------------------
	override bool HandleWeaponFire(CharacterInputContext pInputCtx, float pDt, int pCurrentCommandID)
	{
		if (m_bACE_ForceWeaponFire)
		{
			if (pInputCtx.WeaponIsRaised())
				pInputCtx.SetWeaponPullTrigger(true);
				
			m_bACE_ForceWeaponFire = false;
		}
		
		return HandleWeaponFireDefault(pInputCtx, pDt, pCurrentCommandID);
	}
	
	//------------------------------------------------------------------------------------------------
	void ACE_SetCanHandleWeaponFire(bool canHandle)
	{
		m_bACE_CanHandleWeaponFire = canHandle;
	}
	
	//------------------------------------------------------------------------------------------------
	void ACE_ForceWeaponFire()
	{
		m_bACE_ForceWeaponFire = true;
	}
}

However, this approach does not work when the weapon is lowered, so it's not good for features like weapon cook-off.

Turns out there is already a ticket for it: T166418

I just realized that there is technically already a syntax for it the code base:

class SCR_Sorting<Class T, SCR_SortCompare TCompare>
{
...

but it doesn't seem to be enforced, as the example below still compiles:

class WrongClass
{
	static int Compare(Managed left, Managed right);
}

Thanks for the reply. Looks promising!

Changes were made so that type in JSON is basically cast into script variables if possible.

Does this mean that parsing for other types that defvalue supports will also work?
Like "VETERAN" for EAISkill or "0 1 0" for vector or "0 1 0 1" for Color?

modded also doesn't work:

class test_base<Class T> {};
modded class test_base<Class T> {}; // Throws error

Hello there, issue should be internally fixed but not sure when exactly it will be released. Probably in some next major update.
I will keep the ticket open until it is released so be sure that there are no other issues afterwards,

@Geez, Hi this can be closed, after 60min the update on all servers worked. Maybe the workshop was not ready yet or had todo some background work. I can not close tickets by myself :-( Have a nice week.

Fixed, can close, thank you!

Hi @DarkWolf, most of the issues have been resolved, but the contributor box still resets every time the publish menu is opened.