rails-devel

[Rails-devel] Usage patterns for game history window

[Stefan F. <ste...@we...>]

I am little guessing about the usage of the new game report/history window:
As it is very easy to navigate to past actions of the game, I wonder what the 
user intentions will be:

Will the main use be a possible return to a previous state of the game (for 
example during a ftf game an action was skipped wrongly or a player was 
allowed a take back)?
In that case it make sense to keep the other windows fully activated and 
responsive to user actions. 

After adding the ability to comment the following use case might occur 
frequently in pbem:
Going back to one action, add a comment and return to the end of action stack.

Or maybe it will be more a tool for analyzing the crucial situations after the 
game has finished?
 
The reason is that for the two latter use cases it would be better to disable 
the game windows to user actions to avoid deleting the game history 
unintentionally, preventing a return to the latest game state.
Then there should be a button/menu item (maybe in the Main GameStatus Window 
under Moderator) that allows to restart the game at the selected point in 
history. (=> Replay from here).

Stefan

Re: [Rails-devel] Usage patterns for game history window

[Steve U. <ste...@gm...>]

I see it as useful for analyzing a game after completion, including playing
"what-if" scenarios.

Steve Undy
st...@ro...


On Mon, Aug 16, 2010 at 1:07 PM, Stefan Frey <ste...@we...> wrote:

> I am little guessing about the usage of the new game report/history window:
> As it is very easy to navigate to past actions of the game, I wonder what
> the
> user intentions will be:
>
> Will the main use be a possible return to a previous state of the game (for
> example during a ftf game an action was skipped wrongly or a player was
> allowed a take back)?
> In that case it make sense to keep the other windows fully activated and
> responsive to user actions.
>
> After adding the ability to comment the following use case might occur
> frequently in pbem:
> Going back to one action, add a comment and return to the end of action
> stack.
>
> Or maybe it will be more a tool for analyzing the crucial situations after
> the
> game has finished?
>
> The reason is that for the two latter use cases it would be better to
> disable
> the game windows to user actions to avoid deleting the game history
> unintentionally, preventing a return to the latest game state.
> Then there should be a button/menu item (maybe in the Main GameStatus
> Window
> under Moderator) that allows to restart the game at the selected point in
> history. (=> Replay from here).
>
> Stefan
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

Re: [Rails-devel] Usage patterns for game history window

[Phil D. <de...@gm...>]

I'd agree with Steve, I've been thinking for a while that a 'restart
game from here' and then just clicking 'next action' or something
similar would be a great learning experience for replaying games and
trying out scenarios

(especially after Steve's brutal 1830 victory he just scored over us :p)

On 16 August 2010 20:18, Steve Undy <ste...@gm...> wrote:
> I see it as useful for analyzing a game after completion, including playing
> "what-if" scenarios.
>
> Steve Undy
> st...@ro...
>
>
> On Mon, Aug 16, 2010 at 1:07 PM, Stefan Frey <ste...@we...> wrote:
>>
>> I am little guessing about the usage of the new game report/history
>> window:
>> As it is very easy to navigate to past actions of the game, I wonder what
>> the
>> user intentions will be:
>>
>> Will the main use be a possible return to a previous state of the game
>> (for
>> example during a ftf game an action was skipped wrongly or a player was
>> allowed a take back)?
>> In that case it make sense to keep the other windows fully activated and
>> responsive to user actions.
>>
>> After adding the ability to comment the following use case might occur
>> frequently in pbem:
>> Going back to one action, add a comment and return to the end of action
>> stack.
>>
>> Or maybe it will be more a tool for analyzing the crucial situations after
>> the
>> game has finished?
>>
>> The reason is that for the two latter use cases it would be better to
>> disable
>> the game windows to user actions to avoid deleting the game history
>> unintentionally, preventing a return to the latest game state.
>> Then there should be a button/menu item (maybe in the Main GameStatus
>> Window
>> under Moderator) that allows to restart the game at the selected point in
>> history. (=> Replay from here).
>>
>> Stefan
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>

Re: [Rails-devel] Usage patterns for game history window

[Chris S. <chr...@gm...>]

I would use it to play a pbem forward to explore options, then returning to
the current state to take my actual turn.  You see this behavior in Aliza's
various reports, where she submits files from prospective moves.

I also like the ability to browse through previous game states to figure out
what happened between turns, especially if it is a slow game.

--
Chris

Please consider the environment before printing this e-mail.


On Mon, Aug 16, 2010 at 12:07 PM, Stefan Frey <ste...@we...> wrote:

> I am little guessing about the usage of the new game report/history window:
> As it is very easy to navigate to past actions of the game, I wonder what
> the
> user intentions will be:
>
> Will the main use be a possible return to a previous state of the game (for
> example during a ftf game an action was skipped wrongly or a player was
> allowed a take back)?
> In that case it make sense to keep the other windows fully activated and
> responsive to user actions.
>
> After adding the ability to comment the following use case might occur
> frequently in pbem:
> Going back to one action, add a comment and return to the end of action
> stack.
>
> Or maybe it will be more a tool for analyzing the crucial situations after
> the
> game has finished?
>
> The reason is that for the two latter use cases it would be better to
> disable
> the game windows to user actions to avoid deleting the game history
> unintentionally, preventing a return to the latest game state.
> Then there should be a button/menu item (maybe in the Main GameStatus
> Window
> under Moderator) that allows to restart the game at the selected point in
> history. (=> Replay from here).
>
> Stefan
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>