Debounce player and save updates

[tudddorrr]

No description provided.

[claude]

Code Review - PR #169

🔴 Backwards Compatibility

Breaking API change in TaloPlayer.set_prop() and TaloPlayer.delete_prop() (player.gd:29, 34)

The behavior of these public methods has changed from synchronous to fire-and-forget:

Before:

await Talo.players.update()  # Blocks until server confirms

After:

Talo.players.debounce_update()  # Returns immediately, queues update

Impact: Any user code relying on the update being complete after calling set_prop()/delete_prop() will break. For example:

player.set_prop("score", "100")
# Before: Update is confirmed here
# After: Update is only queued, not confirmed
player.set_prop("level", "2")  # Might overwrite previous update if it hasn't fired yet

Suggestion: Consider one of these approaches:

1. Add a new parameter debounce: bool = false to preserve backwards compatibility
2. Create new methods like debounce_set_prop() and debounce_delete_prop()
3. Document this as a breaking change in release notes and bump the minor version

---

🔵 Code Quality

Redundant content update in update_current_save() (saves_api.gd:133)

When debouncing, the save content is updated locally:

_saves_manager.current_save.content = _saves_manager.get_save_content()

But when the timer fires, update_save() fetches the content again (line 146):

var content := _saves_manager.get_save_content()
save.content = content

Impact: Minor performance cost from double-fetching content. Not a bug, but unnecessary work.

Suggestion: Remove line 133 since the timer will fetch fresh content anyway.

---

✅ Other Categories

Potential bugs: No issues found
Performance: No issues found (debouncing is a performance improvement)
Security: No issues found