Millisecond Forums

Re. #1: You will find this covered in the comments inside the script, starting at line 141:

**************************************************************************************************************
**************************************************************************************************************
EDITABLE LISTS: set the throwing schedules for player 1 and player 3
**************************************************************************************************************
**************************************************************************************************************

Note: by default player 1 and player 3 throw to player 2 roughly 25% of the time (1 out 4 times)

The item lists of these schedules can be further controlled by setting a specific/fixed throw sequence:
Example Player 1:

/items = (3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 2, 3, 2, 3, 3, 3, 3, 3, 3, 3)
/selectionmode = sequence

(if selectionmode = sequence => it is suggested to create the list as long as (values.max_trialcount/2)
to ensure that the beginning of the list does NOT get repeated)

<list player1schedule>
/ items = (3, 3, 3, 2)
/replace = false
</list>

<list player3schedule>
/ items = (1, 1, 1, 2)
/replace = false
</list>

**************************************************************************************************************
**************************************************************************************************************

Re. #2: Add something along the lines of

<trial wait>
/ stimulusframes = [1=waittext]
/ validresponse = (0)
/ trialduration = round(rand(1000,5000))
</trial>

<text waittext>
/ items = ("Waiting for other players to join...")
</text>

and run that trial at the end of <block instructions>

<block instructions>
/ trials = [1=instructions; 2=name; 3=wait]
</block>