8 Commits

Author	SHA1	Message	Date
Starbeamrainbowlabs	c712b502e9	//rotate+: typo in description	2024-06-04 22:43:09 +01:00
Starbeamrainbowlabs	b56bd0d84b	//rotate: fix some minor keyword issues, update reference & changelog ... At some point we need to move the parser to allow for a `player` reference for relative keywords.... or else pass them through somehow	2023-12-16 01:11:25 +00:00
Starbeamrainbowlabs	54c66e0dc9	//rotate: fix bug in which regions are accidentally cut off	2023-12-16 00:35:52 +00:00
Starbeamrainbowlabs	0ac76bc694	//rotate: update pos1/pos2 to bound target region ... ...unfortunately this has exposed a nasty bug!	2023-12-16 00:01:34 +00:00
Starbeamrainbowlabs	9f8cb4d5da	//rotate: add comments on what needs doing to wrangle it into shape	2023-12-14 00:31:12 +00:00
Starbeamrainbowlabs	27aa3a9c8f	It works!! ....but the output seems off when non 90° increments ... ...probably due to the wiping and rotation overlapping	2023-12-13 23:20:32 +00:00
Starbeamrainbowlabs	7d29453699	plug in new //rotate+ logic ... ...but it doesn't work yet currently it crashes with a variety of interesting and colourful error messages working on debugging it now, but it's gonna take a moment	2023-12-13 23:05:00 +00:00
Starbeamrainbowlabs	74a8996afc	//rotate: start implementing a frontend ... This is more complicated than I expected. We've got a new parser and a state machine for the args, but we now need to put these values to use and pass them to worldeditadditions.rotate(). NOTE TO SELF: BE REAL CAREFUL WITH ORIGIN HANDLING. We MUST NOT pull from sorted pos1/2 by accident! Though I doubt this would be an issue since weac.pos.get(player_name, i) is a thing	2023-12-10 03:16:28 +00:00