feb1dd4715
chore: improve changeDojoRoot ( #1522 )
...
Build / build (push) Has been cancelled
Build Docker image / docker (push) Has been cancelled
Using SortId instead of actually changing the component ids.
What's strange is that providing/omitting SortId does seem to make a difference in regards to deco positioning, which is presumably what the POST body would be for. I've opted to simply always provide the SortId in hopes that this avoids the need for repositioning entirely.
Co-authored-by: Sainan <63328889+Sainan@users.noreply.github.com>
Co-committed-by: Sainan <63328889+Sainan@users.noreply.github.com>
2025-04-10 07:15:27 -07:00
0facdd1af9
chore: check permissions for various clan requests ( #1175 )
...
Build / build (18) (push) Successful in 45s
Build / build (20) (push) Successful in 1m4s
Build / build (22) (push) Successful in 41s
Build Docker image / docker (push) Successful in 51s
Reviewed-on: #1175
2025-03-14 07:09:28 -07:00
77aa1caa8f
feat: dojo room destruction stage ( #1089 )
...
Build / build (20) (push) Successful in 38s
Build / build (18) (push) Successful in 57s
Build / build (22) (push) Successful in 56s
Build Docker image / docker (push) Successful in 39s
Closes #1074
Based on what I could find, apparently only rooms need 2 hours to destroy and decos are removed instantly.
Reviewed-on: #1089
2025-03-06 07:19:01 -08:00
36d12e08c7
chore: turn guild DojoComponents into a DocumentArray ( #1070 )
...
Build / build (22) (push) Successful in 35s
Build / build (18) (push) Successful in 53s
Build / build (20) (push) Successful in 57s
Build Docker image / docker (push) Successful in 32s
and use .id for setDojoComponentMessage
Reviewed-on: #1070
2025-03-03 05:46:16 -08:00
7e7e4e2eea
feat: change dojo spawn room ( #949 )
...
Build / build (18) (push) Successful in 36s
Build / build (22) (push) Successful in 56s
Build Docker image / docker (push) Successful in 32s
Build / build (20) (push) Successful in 1m23s
Closes #524
Reviewed-on: #949
Co-authored-by: Sainan <sainan@calamity.inc>
Co-committed-by: Sainan <sainan@calamity.inc>
2025-02-12 14:06:48 -08:00