Remove tests of move_unit's count and move-unit-to-its-own-hex functionality

The count is undocumented on the wiki, and it's causing the schema validation
to fail. The functionality makes sense and I hope it continues to be supported,
but for now let's have a minimal unbreak-the-build change.

Trying to move a unit to the hex occupied by itself causes it to move to a vacant
adjacent hex instead; splitting the move into two separate [move_unit] calls
passes as expected. That sounds reasonable implementation-defined behavior, but
will make a PR to discuss it.
This commit is contained in:
Steve Cotton 2019-12-12 08:47:53 +01:00
parent 7345ca7b0f
commit b479d6f7ac

View file

@ -155,11 +155,13 @@
y=5
[/have_unit]
)}
# test dir with count
# test dir with duplication
# Note: this is intended to be "test dir with count", but that needs the count syntax
# to be added to the schema validation.
[move_unit]
id=bob
dir=sw:3,s:2
dir=sw,sw,sw,s,s
[/move_unit]
{ASSERT (
@ -204,30 +206,6 @@
[/have_unit]
)}
# test dir loop
[move_unit]
id=steve
dir=sw,s,se,ne,n,nw
[/move_unit]
{ASSERT (
[have_unit]
id=alice
x=13
y=8
[/have_unit]
[have_unit]
id=bob
x=7
y=8
[/have_unit]
[have_unit]
id=steve
x=13
y=2
[/have_unit]
)}
# test to_location
[move_unit]
id=alice
@ -247,8 +225,8 @@
[/have_unit]
[have_unit]
id=steve
x=3
y=8
x=13
y=2
[/have_unit]
)}
@ -271,8 +249,8 @@
[/have_unit]
[have_unit]
id=steve
x=3
y=8
x=13
y=2
[/have_unit]
)}