Subject
Replies
Started By
Last Reply
 
Help us help you!
0
1
Resolved (512.1422)
2
Unverified
10
Not a bug
8
Open
3
Resolved
5
Not a bug
1
Resolved (512.1420)
6
Open
16
Open
 
screen_loc not giving correct readings.
1
Open
1
Open
 
Another obscure parser feature that I'm not sure if it ever worked?
6
Resolved (512.1417)
5
Resolved (512.1416)
8
Open
2
Resolved (512.1416)
3
Resolved (512.1416)
 
Special variables used for argument expansion are misbehaving.
4
Resolved (512.1416)
46
Resolved (511.1350)
7
Resolved (512.1414)
4
Resolved (512.1414)
1
Resolved (512.1414)
2
Unverified
 
Easily reproduced, at least.
5
Resolved (512.1414)
6
Deferred
73
Open
2
Not a bug
2
Not a bug
1
Open
17
Open
6
Open
102
Open
13
Resolved (512.1404)
3
Deferred
1
Resolved (512.1412)
 
Probably appearance-related or something.
5
Resolved (512.1412)
 
The order of operations with in, ||, and && is not nice.
19
Verified
 
"in" keyword has less precedence than assignment
3
Open
1
Resolved (512.1411)
7
Resolved (512.1404)
14
Open
1
Open
5
Open
3
Open
 
If world.visibility changes at runtime, these changes do not affect its status on the hub.
Page: 1 2 3
47
Unverified
0
Open
31
Open
2
Open
0
Open
4
Open
0
Open
Page: 1 2 3 ...