From b4157eaedc4a4b58936e262e30e823fecab7b85f Mon Sep 17 00:00:00 2001
From: cameron <86209629+slameron@users.noreply.github.com>
Date: Wed, 2 Apr 2025 15:28:28 -0400
Subject: [PATCH] Fix typo in autotiles snippet
---
_proofs/tiles/autotiles.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_proofs/tiles/autotiles.md b/_proofs/tiles/autotiles.md
index 09b590611..dd5615aea 100644
--- a/_proofs/tiles/autotiles.md
+++ b/_proofs/tiles/autotiles.md
@@ -32,7 +32,7 @@ There are 3 'flavors' of autotiling available:
Why not just always use {% api flixel.tile.FlxTilemapAutoTiling.FULL %}? Your individual project may not need to do all 48 tile configurations, so sticking with just {% api flixel.tile.FlxTilemapAutoTiling.AUTO %} or {% api flixel.tile.FlxTilemapAutoTiling.ALT %} may cut down on the number of tiles you need to draw.
- Note: You can use
customTileRemap to build your own auto-tiling map logic. This is especially useful if you want to use something like {% api flixel.addons.tile.FileTilemapExt %} to do slopes, as an example.
+ Note: You can use
customTileRemap to build your own auto-tiling map logic. This is especially useful if you want to use something like {% api flixel.addons.tile.FlxTilemapExt %} to do slopes, as an example.
```haxe
map.loadMapFromCSV(mapData, tilesImage, tileWidth, tileHeight, FlxTilemapAutoTiling.AUTO);