Comments on: Feedback For Better IF Parsing http://orangeriverstudio.com/monksbrew/2008/11/feedback-for-better-if-parsing/ Anecdotes on the adventure of indie game development Sun, 05 Feb 2012 00:59:02 +0000 hourly 1 By: El Clérigo Urbatain http://orangeriverstudio.com/monksbrew/2008/11/feedback-for-better-if-parsing/comment-page-1/#comment-168 El Clérigo Urbatain Mon, 10 Nov 2008 12:07:00 +0000 http://orangeriverstudio.com/monksbrew/?p=76#comment-168 Curiously enough I've dropped a suggestion about that kind of system (a tester interface) in the Emily Short's blog. I don't pretend to press her to build that kind of thing, but I find her "collaborator interface" of her project "Alabaster" to be a first step in this direction everyone is talking about here. You can cast an eye to it at:<br/>http://emshort.wordpress.com/2008/11/09/alabaster-interim-status-report-release-18/ Curiously enough I’ve dropped a suggestion about that kind of system (a tester interface) in the Emily Short’s blog. I don’t pretend to press her to build that kind of thing, but I find her “collaborator interface” of her project “Alabaster” to be a first step in this direction everyone is talking about here. You can cast an eye to it at:
http://emshort.wordpress.com/2008/11/09/alabaster-interim-status-report-release-18/

]]> By: Anonymous http://orangeriverstudio.com/monksbrew/2008/11/feedback-for-better-if-parsing/comment-page-1/#comment-167 Anonymous Thu, 06 Nov 2008 19:32:00 +0000 http://orangeriverstudio.com/monksbrew/?p=76#comment-167 grrrr it lost my comment (last time I try the openid option).<br/><br/>Basically I don't think this kind of after-release testing is probably needed; beta testing is. Three things:<br/><br/>1) why not implement tool support to make beta-testing easier, eg a command that marks the last response as inadequate.<br/><br/>2) are there already sites to help authors looking for beta-testing, if so can these be promoted inside authoring software<br/><br/>3) can there be community encouragement of testing eg restrict competition entries or reduce prominence of IF Archive listing for games that aren't sufficiently beta-tested<br/><br/>'New to IF' users pose a different problem, I think this can better be addressed by interpreter/system-provided tutorials. grrrr it lost my comment (last time I try the openid option).

Basically I don’t think this kind of after-release testing is probably needed; beta testing is. Three things:

1) why not implement tool support to make beta-testing easier, eg a command that marks the last response as inadequate.

2) are there already sites to help authors looking for beta-testing, if so can these be promoted inside authoring software

3) can there be community encouragement of testing eg restrict competition entries or reduce prominence of IF Archive listing for games that aren’t sufficiently beta-tested

‘New to IF’ users pose a different problem, I think this can better be addressed by interpreter/system-provided tutorials.

]]> By: Bruce http://orangeriverstudio.com/monksbrew/2008/11/feedback-for-better-if-parsing/comment-page-1/#comment-166 Bruce Wed, 05 Nov 2008 22:48:00 +0000 http://orangeriverstudio.com/monksbrew/?p=76#comment-166 I've been working on a web-based IF engine based on this very concept, where the parser uses standard NL corpus tagging, hinted by statistical inputs based on gameplay (globally or specific to a game). It's a simple idea that applies best in collaborative environments.<br/><br/>In addition to statistical methods for noun or verb extensions, you can build up libraries of sentence structures, helpful for properly dissecting colloquialisms and shorthands that arise within given games or age groups of users.<br/><br/>The approach I've taken with this problem is to collect the transcripts for each game, presenting them in the author view along side the chapter/location/object definitions as missed cases (or events). A summary is available of the common problems globally as well, to give an author an idea of both the sticking points in the game, and opportunities for better immersion. I’ve been working on a web-based IF engine based on this very concept, where the parser uses standard NL corpus tagging, hinted by statistical inputs based on gameplay (globally or specific to a game). It’s a simple idea that applies best in collaborative environments.

In addition to statistical methods for noun or verb extensions, you can build up libraries of sentence structures, helpful for properly dissecting colloquialisms and shorthands that arise within given games or age groups of users.

The approach I’ve taken with this problem is to collect the transcripts for each game, presenting them in the author view along side the chapter/location/object definitions as missed cases (or events). A summary is available of the common problems globally as well, to give an author an idea of both the sticking points in the game, and opportunities for better immersion.

]]>