ZDoom

Zdoom's decorate only relies upon jumping if successful. Change "state fail" to "state success" IMO, and it will be good to go. Better consistency this way. It's how state jumps are made all throughout with jumping functions.

I remember when A_SetProperty was a thing..

:P

[quote="Nightfall"]It shouldn't need [i]three[/i] fail states... one is enough. A_SetSize([i]int[/i] height, [i]int[/i] radius, [i]int[/i] flags [, [i]state[/i] fail])[/quote]
This might sound better and reasonable than A_SetHeight and A_SetRadius, although I'm still waiting for a Yes or No on this suggestion though...
EDIT: first post edited.

[quote]A_SetSize(string height, string radius...[/quote]
Why 'string'? Shouldn't they be integers?

It shouldn't need [i]three[/i] fail states... one is enough. A_SetSize([i]int[/i] height, [i]int[/i] radius, [i]int[/i] flags [, [i]state[/i] fail])

Would something like this make sense:

A_SetSize([i]int[/i] height, [i]int[/i] radius, [i]int[/i] flags [, [i]state[/i] fail_height [, [i]state[/i] fail_radius [, [i]state[/i] fail_both]]])
EDIT: Yes, int is what it should have been. Fixed

Theoretically, you could make it default behavior to fail a size change if the result would not fit. However, a flag to disable this check could be needed in certain cases.

script 725 (void) //Checks if Cyclops uncompressed fits where the player tried to summon it, if yes keep the spawning process
{
	int x = GetActorX(0);
	int y = GetActorY(0);
	int z = GetActorZ(0);
	
	if (!Spawn("CyclopsTestBox",x,y,z,0,GetActorAngle(0) >> 8))
	{
		SetResultValue ( False );
	}
	
	else
	{
		SetResultValue ( True );
	}
}

Actually i made a Script for Hunter's Moon V2.6 that checks if the vehicles fits in the place that the players wants decompress them, if it doesn't have enough size it denies the decompression.

It's very simple and checks the size by trying spawn a invisible actor that have the same size of the vehicle decompressed, if the spawn fails it tell to the Vehicle actor to not spawn the vehicle there, it have a duration of 2 tics, then disappears.

Maybe something of the kind can be made using some system of collision checking, with a hybrid actor that take the desired size of the thing that will have the collision changed.

[code]script 725 (void) //Checks if Cyclops uncompressed fits where the player tried to summon it, if yes keep the spawning process
{
int x = GetActorX(0);
int y = GetActorY(0);
int z = GetActorZ(0);

if (!Spawn("CyclopsTestBox",x,y,z,0,GetActorAngle(0) >> 8))
{
SetResultValue ( False );
}

else
{
SetResultValue ( True );
}
}[/code]

It wouldn't really be that hard to make some stuff in decorate that would be run beforehand to make sure that the object had enough room to change the Radius/Height.

[quote="Nash"]It's easy to do (literally just takes a few lines to add in the source code; I've already done it in my source fork) but the argument of not adding it into official versions is that the actors might get stuck in level geometry/inside other actors if these two commands aren't used sparingly...

(Not a very strong argument, in my opinion - there are already other ways to abuse the engine and break levels :P)[/quote]

Agree.

With this added or not, if someone wants joke with Actor's Collision, they will do via ACS however, for me those commands avoid the essencial use of ACS to change a Actor's collision size, making less hacks using ACS or MorphPowerups.

It's easy to do (literally just takes a few lines to add in the source code; I've already done it in my source fork) but the argument of not adding it into official versions is that the actors might get stuck in level geometry/inside other actors if these two commands aren't used sparingly...

(Not a very strong argument, in my opinion - there are already other ways to abuse the engine and break levels :P)

Just like [wiki]A_SetMass[/wiki], but two more functions easier to use instead of hacky workarounds... thoughts?
EDIT: or how about A_SetSize(int height, int radius, int flags [, state fail])