douglowe wrote:I think it's more of a differing interpretation (or, misinterpretation, if you like ;)) of the rules by cyanide than an actual bug. When I played TT dungeonbowl with friends we ruled that it was just movement onto the teleporter which activates it - but cyanide are interpreting it as being any action on the teleporter (be it a move or a block) activates it (I think it's also activated if you're standing on the teleporter and get knocked down where you are, which doesn't seem right to me either).
The rules are actually clear and explicit about this. There is no room for interpretation.
Dungeonbowl rules, page 3, "TELEPORTING":
"When a player moves onto a pad, roll a D6. The player is immediately teleported to the pad with the same number."
"When a player moves onto a pad". That is, when they voluntarily step onto a pad or when they are pushed there. Not when they do something or anything while standing on a pad. Not while they have something or anything done to them while standing on a pad. Not blocking or being blocked on a pad.
Cyanide's decisions on this, conscious or incidental to the program code implementation, are not interpretations. They are rule changes.
It is a great pity Cyanide has not explicitly, clearly and above all comprehensively listed their rule changes anywhere. They could still help us the players out a great deal by doing just that. Cyanide, if you are listening, could you please create a list of the Cyanide Dungeonbowl rule differences from the two Games Workshop rule books on the game web site? I'm sure active volunteers will appear to help you with the work if you need them, but it is you who would need to get the ball rolling.
Actually, when in comes to Cyanide documentation about teleportation, the game manual has this to say on page 35:
"Teleporters
There are teleporters in a dungeon. A player need only step on one to use it"
That is all that is said about it and you are told to see the Games Workshop rules for further information. This means there should be no teleporting on blocks even according to Cyanide's own documentation. So the current situation is not just a rule change, it is an undocumented rule change. Fun times.