Fix sigsegv caused by bad target check in A_Custom3DRotate
it checked for a target too late so if you try to use it with no target the game crashes
also prevents a console flood outside of devmode if the object has no speed
Is it intentional that you removed a
cv_debugcheck from one of the debugging prints, yet added it to the other? (It looks good to me, I'm just making sure that it's intentional.)
Since the first error removes the object entirely, I figured the error should be thrown regardless so someone doesn't get confused why their thing isn't working. The speed error isn't as important and will flood the console, so I restricted it to devmode.
mergedToggle commit list