-
Notifications
You must be signed in to change notification settings - Fork 2
/
future.html
122 lines (114 loc) · 5.97 KB
/
future.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>TAEB - Future Directions</title>
<link rel="stylesheet" type="text/css" href="style/main.css" />
<link rel="icon" type="image/png" href="image/taeb-icon.png" />
<meta http-equiv="content-type" content="text/html;charset=utf-8" />
</head>
<body>
<div id="main">
<div id="content">
<h1>TAEB - Future Directions</h1>
<h2><a name="announce">Announcements</a></h2>
<p>
See
<a href="http://taeb-blog.sartak.org/2009/03/taeb-pubsub-and-announcements.html">TAEB, pubsub, and announcements</a>
on our blog.
</p>
<h2><a name="monster-tracking">Monster Tracking</a></h2>
<p>
Currently, TAEB completely forgets about monsters when they
are not visible. It rediscovers them on the next turn and
generally acts correctly, but not being able to track monster
state from turn to turn puts annoying limitations on our
tactics. If we could somehow track monsters the way we track
items, TAEB would potentially be a much better fighter.
</p>
<p>
Most significantly, it is impossible for TAEB to know if a
monster is awake; since it never remembers seeing monsters
before, it is forced to conservatively assume the monster is
asleep. If a monster is potentially asleep, we can't use
combat tactics like waiting in a corridor - we would wait
forever! This is an especially annoying problem because
valkyries start with Stealth, so zoo monsters are very often
asleep.
</p>
<p>
Unfortunately, monster tracking is hard. Monsters move around
much more than items, so in general it's impossible to know
<i>which</i> monsters are the same as monsters on the previous
turn, especially in pack situations. We really want to
support tracking packs, because pack monsters are a major TAEB
killer. Also, monsters have many hidden variables, and
testing in combat doesn't work very well.
</p>
<p>
The best candidate solutions are based on variations of
<a href="http://en.wikipedia.com/wiki/Bayesian_inference">
Bayesian inference</a>, deciding for each monster a
conditional probability of being something we care about.
This is a fair amount of work, though, and little progress has
been made.
</p>
<h2><a name="newais">New AIs</a></h2>
<p>
Behavioral, time-tested as it is, is starting to show signs of
having reached the limits of its extensibility. Each new
behavior added slows down the bot additively, and in
interesting environments like quest levels we may take several
seconds to decide on each move. Can Behavioral be saved or
will a new, more stateful AI like <a
href="planar.html">Planar</a> take the torch?
</p>
<h2><a name="ih3">Interhack III</a></h2>
<p>
One long-term idea for the TAEB core is to use it to power the
next-generation of <a
href="http://interhack.us/">Interhack</a>. This would
result in an Interhack with ability to semi-automate arbitrary
tasks, extremely flexible Perl scriptability, and a queriable
model of the entire dungeon, enabling an interface to rival
Crawl. There are two main blockers for this. First, TAEB has
to support all NetHack commands and game mechanics. While old
Interhack could get away with simply passing through
unrecognized commands and output (nearly all of it), that
would wreak havoc with TAEB's world model. Second, TAEB needs
to become much faster; on a good day, TAEB processing lag is
on the order of a third of a second, more than twice the
network lag from San Diego to Helsinki.
</p>
</div>
</div>
<div id="sidebar">
<div id="nav">
<h3>TAEB</h3>
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="history.html">History</a></li>
<li><a href="design.html">Design</a></li>
<li><a href="future.html">Future directions</a></li>
<li><a href="bugs.html">Bugs and limitations</a></li>
<li><a href="bots.html">Other bots</a></li>
<li><a href="http://taeb-blog.sartak.org">Design and development blog</a></li>
<li><a href="http://twitter.com/nhtaeb">@nhtaeb on Twitter</a></li>
<li><a href="http://github.com/sartak/TAEB">Browse code</a></li>
<li><a href="http://github.com/sartak/taeb.sartak.org">Site's code</a></li>
</ul>
<h3>Developers</h3>
<ul>
<li><a href="http://sartak.org">Shawn M Moore (sartak)</a></li>
<li><a href="http://tozt.net">Jesse Luehrs (doy)</a></li>
<li>Stefan O'Rear (sorear)</li>
<li><a href="http://mathemaniac.org/">Sebastian P. (Sebbe)</a></li>
<li><a href="http://katron.org">Sean Kelly (arcanehl)</a></li>
<li>Anthony Boyd (sawtooth)</li>
<li>Alex Smith (ais523)</li>
</ul>
</div>
</div>
</body>
</html>
<!-- vim: set tw=70 si: -->