|
|
Downloads
|
|
- Download ScriptEase for Neverwinter Nights
-
IMPORTANT: If you have created your own atoms and patterns in a
previous version of ScriptEase using the Encounter Designer or Atom
Designer, you MUST export them and back up your module before opening
it in ScriptEase 1.3 or later.
- Download individual components:
- ScriptEase Winter 2009 Beta Program (ScriptEase_w2009beta.jar).
Linux and Mac users will want to download this file instead of the installer.
Please consult these instructions.
- Tutorials for ScriptEase Winter 2009 Beta
- Tutorial: Making Your World (World.pdf)
, the world building tutorial
- Tutorial: Making Your World Work (WorldWork.pdf)
, the basic encounter pattern tutorial
- Tutorial: Making Your World Interesting (WorldInteresting.pdf)
, the advanced conversation tutorial
- Tutorial: Making Your World Leverly (WorldLeverly.pdf)
, the condition and plot token tutorial
- Tutorial: Making Your World Fleshy (WorldFleshy.pdf)
, the behaviour pattern tutorial
- Tutorial: Making Your World Story-worthy (WorldStoryworthy.pdf)
, the quest pattern tutorial
- ScriptEase 1.8.1 Program (ScriptEase.jar).
- Tutorial for ScriptEase 1.8.1
- Tutorial: ScriptEase and NWN Aurora Toolset (Tutorial.doc)
- Map: The map of the castle used by the tutorial. (Maps.doc)
- Empty Castle Module (Toolset Tutorial) (CastleEmpty.mod).
Depending on your
browser's behavior, you may not be asked to save
your module when you click on the module link; in this case, right-click
on the
link and then choose "Save Target As...". Save this module in the
NWN/modules folder.
- Full Castle Module (Finished Toolset Tutorial) (CastleFull.mod).
Save this module in the NWN/modules folder.
- Scripted Castle Module (Finished ScriptEase Tutorial) (CastleFullSE.mod).
Save this module in the NWN/modules folder.
|
|
ScriptEase
|
|
Making a module for a game like BioWare's Neverwinter Nights is a new
way of telling a story, and has its own set of challenges. Instead of
readers, you have players who want to feel as though they actively
participate in the story. One way to do this is to present your
players with a world that they interact with, instead of one they just
pass through.
ScriptEase is a tool designed to complement Bioware's Aurora Toolset.
With Aurora, you construct the world the players will adventure in, and
with ScriptEase you bring it to life.
|
|
About the Team
|
|
ScriptEase is being developed by researchers from two research groups
in the Department of Computing Science at the University of Alberta,
the Games group and the Software Systems group. The goal of the
ScriptEase project is to support module builders (storytellers) and
game designers in automatically generating scripts for computer
role-playing stories, without programming.
Current Participants
Past Participants:
- Ana Alcantara was a writer.
- Stephie Cadek, Graeme Haugen, and Joyce Lam were high-school summer interns.
- Stephanie Gillis is a teacher in Edmonton and wrote the current crop of
ScriptEase tutorials.
- Sabrina Kratchmer worked with the ScriptEase team as a WISEST summer student.
- Matthew McNaughton was a programmer analyst in the Computing Science
department. He is currently working on his PhD in robotics at CMU.
- Curtis Onuczko was a MSc graduate student in Computing Science.
- Dominique Parker was a programmer-analyst in the Computing Science
department and went on to work at Electronic
Arts.
- John Peters was an NSERC summer student.
- Emma Rapati was a B.Sc. summer student.
- James Redford worked on ScriptEase as an M.Sc. graduate student, and
is now at BioWare.
- Thomas Roy was an IIP (intern) programmer analyst.
- Lisa Stewart wrote the original tutorial for the first release of
ScriptEase.
- Kevin Waugh was an IIP programmer analyst.
- Danielle Wiebe was a WISEST student.
|
|
Feedback
|
- Please send feedback to scriptease@cs.ualberta.ca. Or, if you
have a BioWare forums account, post to the ScriptEase topic in the NWN Scripting forum.
- If you use ScriptEase to script a module, please send us the name
of
the module, the author(s) name, a web-link to the module and an
indication of what percentage of the scripting in the module was
generated using ScriptEase (for example 100% means no scripts were
added by hand) and we will include it in our ScriptEase Module list.
|
|
|