Closed OttoHatt closed 3 days ago
Let's make a new maid specifically for the keys instead of trying to fix the :GiveTask() call. That way future changes won't break anything.
We should also maybe add a method to Maid that allows you to get/set a task that could conflict with a name. For example. GiveTask
as a key could be really bad.
We should consider adding maid:Set() or something for safety.
:rocket: PR was released in @quenty/adorneeboundingbox@8.3.1
, @quenty/gameconfig@12.7.1
, @quenty/gameproductservice@14.7.1
, @quenty/highlight@10.4.1
, @quenty/inputkeymaputils@14.6.2
, @quenty/observablecollection@12.3.1
, @quenty/scoredactionservice@16.7.2
, @quenty/settings-inputkeymap@10.8.2
, @quenty/settings@11.6.1
, @quenty/soundgroup@1.3.1
:rocket:
The maid is given some cleanup w/
:GiveTask
, so they get given keys1
and2
internally. The value brios are also put into this maid, so if you didmap:Set(1, ...)
you'd break everything observing the container.