|  |  |  | Properties that are objects may be inspected with the dot syntax. | 
|  |  |  |  | 
|  |  |  | Current available actions are verify target and assign variable. | 
|  |  |  |  | 
|  |  |  | ## Examples | 
|  |  |  |  | 
|  |  |  | When used as part of the targeting column's card property, player property, or game property fields, the context is automatically assumed to be the target card, player, or game. | 
|  |  |  |  | 
|  |  |  | In these examples these expressions are placed in the card property field: | 
|  |  |  |  | 
|  |  |  | ``` javascript | 
|  |  |  | _effectTriggers.invoke // returns an array of effect lines with the invoke trigger of the target card. | 
|  |  |  | _originals.health // returns the original health of the card before modification. | 
|  |  |  | ``` | 
|  |  |  |  | 
|  |  |  | In these examples these expressions are placed in the card property field: | 
|  |  |  |  | 
|  |  |  | ``` javascript | 
|  |  |  | hand[5] // returns the ciid of the 6th card in the target player's hand. | 
|  |  |  | ``` | 
|  |  |  |  | 
|  |  |  | When not used as part of the targeting column's card property, player property, or game property fields, you must specify a context as the first identifier. Some special identifiers can be used. `"game", "owner", "opponent", "thisCard"` | 
|  |  |  |  | 
|  |  |  | ``` javascript | 
|  |  |  | game.player1.hand // returns an array with the hand of player 1. This is NOT equivalent to using an assign variable on the hand, as that returns a COPY of the hand array. Modifying this array will modify the hand itself (not recommended). | 
|  |  |  | thisCard._effectTriggers.invoke // returns an array of effect lines with the invoke trigger | 
|  |  |  | owner.mana // returns the mana of the owner of this card. | 
|  |  |  | ``` | 
|  |  |  | \ No newline at end of file |