Still an issue with "nothing interesting happens"

[GregHib]

Continuing from #989

This is more a fundamental issue with how interaction works. I don't think things should be called a second time even when suspended. Should resumeSuspension() even belong in Interact?

When you interact with some things. e.g. setting up pitfall traps.

1. Interact with object
2. Object has suspend and replace
3. As object has suspended interactionFinished() returns false and the interact loop tries again next tick
4. Second attempt fails as the object now has a different id i.e. Trap:pitfall_0 (which is invalid) and so hasOperate() and hasApproach() fail and if the player is withinMelee noInterest() is called instead.