Unconditional multiple undo's would require a rewrite of Poser code. Now we'd all like that for a number of reasons totally unrelated to undo's!!! But if it hasn't happened to date, in fact not even a part of the core Poser code has been rewritten in what 10 years, or ever, then it ain't likely to happen anytime soon for a trivial - in marketing terms - reason like no undo's. But a conditional multiple undo might be do-able without a rewrite. Changing dial values for example doesn't require any complex state retention, just store the prior value(s) and redo the action to equate to an undo. That should be easy to do and deterministic enough (ie. what is covered by multiple undo and when) to be viable.