Fix the floating sword-block exploit.
Pretty much what I was trying to do before, only instead of forcing the block to a position, we continue to let the loop attempt to find a rotation that works. Let's test and see how we like this. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2927 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
//
|
||||
// $Id: DropBoard.java,v 1.1 2003/11/26 01:42:34 mdb Exp $
|
||||
// $Id: DropBoard.java,v 1.2 2003/12/31 00:03:14 ray Exp $
|
||||
|
||||
package com.threerings.puzzle.drop.data;
|
||||
|
||||
@@ -248,6 +248,7 @@ public abstract class DropBoard extends Board
|
||||
// if our piece is facing south and we're using radial
|
||||
// rotation then we need to try popping the piece up a row to
|
||||
// check for a fit
|
||||
/*
|
||||
if (rtype == RADIAL_ROTATION && orient == SOUTH) {
|
||||
// check if our hypothetical new coordinates are empty
|
||||
if (isBlockEmpty(ox, oy - 1,
|
||||
@@ -261,6 +262,7 @@ public abstract class DropBoard extends Board
|
||||
return new int[] { orient, px, py - 1 };
|
||||
}
|
||||
}
|
||||
*/
|
||||
}
|
||||
|
||||
// this should never happen since even in the most tightly
|
||||
|
||||
Reference in New Issue
Block a user