v3.1.0: fixed wrong cases if canPlaceChar called super.canPlaceItem

in these cases both super methods did the same thing so this changes no actual functionality
This commit is contained in:
Evan Debenham
2025-03-26 14:51:08 -04:00
parent 61a68b2fe3
commit c5f1025478
3 changed files with 3 additions and 3 deletions

View File

@@ -76,7 +76,7 @@ public class RitualSiteRoom extends StandardRoom {
@Override
public boolean canPlaceCharacter(Point p, Level l) {
return super.canPlaceItem(p, l) && l.distance(CeremonialCandle.ritualPos, l.pointToCell(p)) >= 2;
return super.canPlaceCharacter(p, l) && l.distance(CeremonialCandle.ritualPos, l.pointToCell(p)) >= 2;
}
public static class RitualMarker extends CustomTilemap {

View File

@@ -66,7 +66,7 @@ public class CavesFissureRoom extends StandardRoom {
@Override
public boolean canPlaceCharacter(Point p, Level l) {
return super.canPlaceItem(p, l) && l.map[l.pointToCell(p)] != Terrain.EMPTY_SP;
return super.canPlaceCharacter(p, l) && l.map[l.pointToCell(p)] != Terrain.EMPTY_SP;
}
@Override

View File

@@ -58,7 +58,7 @@ public abstract class StandardBridgeRoom extends StandardRoom {
@Override
public boolean canPlaceCharacter(Point p, Level l) {
return super.canPlaceItem(p, l) && (spaceRect == null || !spaceRect.inside(p));
return super.canPlaceCharacter(p, l) && (spaceRect == null || !spaceRect.inside(p));
}
//keep these so that subclasses can use them in their methods