humza/sml-projects
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
94dc17011ee8cab3aef08ce761e643e789d5871b
sml-projects/fcore/level/enemy/enemy-patch.sml

339 lines
6.7 KiB
Standard ML
Raw Normal View History

derive EnemyPhysics module from functor
2025-01-12 23:33:20 +00:00
signature ENEMY_PATCH =
sig
datatype enemy_patch =
W_HEALTH of int
| W_X of int
| W_Y of int
refactor file order in preparation for adding GapMap for enemy
2025-02-13 11:24:44 +00:00
| W_X_AXIS of EntityType.x_axis
| W_Y_AXIS of EntityType.y_axis
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
| W_PLAT_ID of int
better path landing implemented, making sure enemy fully overlaps platform they are trying to reach, and enemy's jump is clearer (before, when enemy landed on platform, they went straight to the top of the platform, but now they jump a little over the platform which looks clearer)
2025-01-26 13:23:20 +00:00
| W_NEXT_PLAT_ID of int
initial implementation of bat's update function (todo: make bat oscillate up and down while it also moves in x axis, and also code bat's collisions with player, adding to falling list if necessary, or being filtered by player's attack)
2025-02-11 19:38:02 +00:00
| W_BAT_REST of int
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
| W_BAT_MAX_Y of int
| W_BAT_MIN_Y of int
refactor file order in preparation for adding GapMap for enemy
2025-02-13 11:24:44 +00:00
| W_BAT_DIR_Y of EnemyType.bat_dir_y
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
| W_FACING of EntityType.facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
| W_SHIELD_ON of bool
derive EnemyPhysics module from functor
2025-01-12 23:33:20 +00:00
refactor file order in preparation for adding GapMap for enemy
2025-02-13 11:24:44 +00:00
val withPatch: EnemyType.enemy * enemy_patch -> EnemyType.enemy
derive EnemyPhysics module from functor
2025-01-12 23:33:20 +00:00
refactor file order in preparation for adding GapMap for enemy
2025-02-13 11:24:44 +00:00
val withPatches: EnemyType.enemy * enemy_patch list -> EnemyType.enemy
derive EnemyPhysics module from functor
2025-01-12 23:33:20 +00:00
end
structure EnemyPatch: ENEMY_PATCH =
create enemy patch structure
2025-01-12 23:28:03 +00:00
struct
datatype enemy_patch =
W_HEALTH of int
| W_X of int
| W_Y of int
refactor file order in preparation for adding GapMap for enemy
2025-02-13 11:24:44 +00:00
| W_X_AXIS of EntityType.x_axis
| W_Y_AXIS of EntityType.y_axis
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
| W_PLAT_ID of int
better path landing implemented, making sure enemy fully overlaps platform they are trying to reach, and enemy's jump is clearer (before, when enemy landed on platform, they went straight to the top of the platform, but now they jump a little over the platform which looks clearer)
2025-01-26 13:23:20 +00:00
| W_NEXT_PLAT_ID of int
initial implementation of bat's update function (todo: make bat oscillate up and down while it also moves in x axis, and also code bat's collisions with player, adding to falling list if necessary, or being filtered by player's attack)
2025-02-11 19:38:02 +00:00
| W_BAT_REST of int
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
| W_BAT_MAX_Y of int
| W_BAT_MIN_Y of int
refactor file order in preparation for adding GapMap for enemy
2025-02-13 11:24:44 +00:00
| W_BAT_DIR_Y of EnemyType.bat_dir_y
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
| W_FACING of EntityType.facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
| W_SHIELD_ON of bool
create enemy patch structure
2025-01-12 23:28:03 +00:00
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
fun mkEnemy
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
) =
slight refactoring to help with extensibility of adding enemy variants later
2025-01-14 11:50:27 +00:00
{ id = id
, health = health
, x = x
, y = y
, xAxis = xAxis
, yAxis = yAxis
, variant = variant
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
, platID = platID
better path landing implemented, making sure enemy fully overlaps platform they are trying to reach, and enemy's jump is clearer (before, when enemy landed on platform, they went straight to the top of the platform, but now they jump a little over the platform which looks clearer)
2025-01-26 13:23:20 +00:00
, nextPlatID = nextPlatID
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
, batRest = batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY = batDirY
, batMaxY = batMaxY
, batMinY = batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing = facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn = shieldOn
slight refactoring to help with extensibility of adding enemy variants later
2025-01-14 11:50:27 +00:00
}
create enemy patch structure
2025-01-12 23:28:03 +00:00
fun withPatch (enemy, patch) =
let
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
val
{ id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
} = enemy
create enemy patch structure
2025-01-12 23:28:03 +00:00
in
case patch of
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
W_HEALTH health =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
fix compile errors after previous commit (which involved reimplementing the quad tree to eliminate the possibility of a class of bugs I was experiencing; the problem was that the quad bounds were being passed recursively in different functions, but the long argument list in these functions made it difficult to see where the mismatch was)
2025-01-27 23:41:59 +00:00
| W_X x =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
| W_X_AXIS xAxis =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
fix compile errors after previous commit (which involved reimplementing the quad tree to eliminate the possibility of a class of bugs I was experiencing; the problem was that the quad bounds were being passed recursively in different functions, but the long argument list in these functions made it difficult to see where the mismatch was)
2025-01-27 23:41:59 +00:00
| W_Y y =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
| W_Y_AXIS yAxis =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
refactor player and enemy records to have a platID field (representing the last platform that player or enemy stood on), and fix resulting compile errors
2025-01-25 08:41:42 +00:00
| W_PLAT_ID platID =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
better path landing implemented, making sure enemy fully overlaps platform they are trying to reach, and enemy's jump is clearer (before, when enemy landed on platform, they went straight to the top of the platform, but now they jump a little over the platform which looks clearer)
2025-01-26 13:23:20 +00:00
| W_NEXT_PLAT_ID nextPlatID =>
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
begin adding variant for STRAIGHT_BAT enemy
2025-02-11 18:05:44 +00:00
)
initial implementation of bat's update function (todo: make bat oscillate up and down while it also moves in x axis, and also code bat's collisions with player, adding to falling list if necessary, or being filtered by player's attack)
2025-02-11 19:38:02 +00:00
| W_BAT_REST batRest =>
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
)
| W_BAT_MAX_Y batMaxY =>
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
)
| W_BAT_MIN_Y batMinY =>
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
add fields to enemy which are relevant to bat's state
2025-02-11 23:54:13 +00:00
)
| W_BAT_DIR_Y batDirY =>
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
add 'facing' field to enemy, and update that field when enemy starts moving in different direction (with regards to x_axis)
2025-02-15 08:13:36 +00:00
)
| W_FACING facing =>
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
, facing
begin adding shield slime enemy variant
2025-02-15 12:34:10 +00:00
, shieldOn
)
| W_SHIELD_ON shieldOn =>
mkEnemy
( id
, health
, x
, y
, xAxis
, yAxis
, variant
, platID
, nextPlatID
, batRest
, batDirY
, batMaxY
, batMinY
, facing
, shieldOn
initial implementation of bat's update function (todo: make bat oscillate up and down while it also moves in x axis, and also code bat's collisions with player, adding to falling list if necessary, or being filtered by player's attack)
2025-02-11 19:38:02 +00:00
)
create enemy patch structure
2025-01-12 23:28:03 +00:00
end
fun withPatches (enemy, lst) =
case lst of
hd :: tl =>
let val enemy = withPatch (enemy, hd)
in withPatches (enemy, tl)
end
| [] => enemy
end
Reference in New Issue Copy Permalink