kellyelton/OCTGN — Issue #24: Manipulating cards you own but don't control 
Author: brine
Created: 2012-01-31 16:13:55+00:00
State: open

There has always been an issue with OCTGN involving the manipulation of cards you own but don't control; Jods knew about it for years but never figured out a way to fix it. He mentions in the Python API wiki page:

"As of OCTGN 0.9, the Python scripts do not enforce controlship on the object they manipulate. It is not safe to change the state of cards or groups you don't control, even though the script would let you do that. The only functions that are safe to use on elements you don't control are target, highlight, counters and markers manipulations. Of course you can read the state of any element.
So be very careful to always filter the cards you touch. DO NOT use (c for c in table); DO use (c for c in table if c.controller == me).

This issue can cause OCTGN to crash in the case where a python function tries to move a card on the table at the same time that another player is trying to manipulate that card (such as click-dragging it around the table). The "Scoop" function in MTG provides an example of where such a crash may occur, as it attempts to return cards you own but no longer control to your deck.

This whole issue is probably a consequence of the way OCTGN handles objects, so I can't imagine a simple fix (if a fix can even exist). However, I feel it's important to note that this issue exists in the event someone else runs into it