The ticket purchase code changed with the latest version to automatically consolidate the amount needed for a ticket with the fee in a regular transaction, then purchase the ticket with no change, instead leaving the change in a regular transaction so that it won't get stuck leaving the user completely unable to spend the remainder of their funds.The side effect, as you noticed, is that the transactions generating outputs to be consumed as tickets go into the blockchain even if the tickets fail to, spending a small amount of fees. The automatic ticket purchase code was only intended to be used for simulation testing originally, but this sort of thing tends to get picked up and then never dropped. So, it's a trade off. Most people want to be able to spend their funds and not have them stuck while they wait to see if their ticket will ever get into a block.I'm working on a simple, customizable drop-in replacement for automating ticket purchase ASAP, using the RPC client code. Today I got a new RPC call for daemon merged that tracks fees in the mempool, current blocks, and previous whole difficulty windows . The new ticket purchasing bot will use the purchaseticket RPC API directly and track fee indicators for tickets along with difficulty, and spread ticket purchases over multiple difficulties while still attempting to get the majority of tickets for the lowest price.There was also a bug in wallet before where ticket fee wasn't selecting fees per KB. This has been fixed and setting the ticket fee now sets correctly. Because of this, it looks like people were setting their fees much to low with the new version.The new ticket purchaser is coming, but one thing at a time. Sorry to not have clear documentation for the API change, but we're also trying to get stakepools up to speed ASAP and there's a lot of work to be done in a short period of time.