suggestions:
why?
we know that a lot of people buy/sell mimu keys in #share・n・swap and sometimes these keys are not used right away. by having this feature it can help both sellers/buyers have better management over their keys and remove the chance of accidentally using keys they sold.
it’d be cool if it could send in dms too and/or users being able to use keys inside mimu’s dms to avoid sniping
don’t really know if the last one is possible
/keys list
is now a thing to see the key codes.
🥺 just wanted to bump this since I know it was partially implemented! would really appreciate a /keys transfer type cmd ♡
if it’s hard to add the way kiiko suggested (tho I do pref that way!), maybe have smt like /keys claim inventory/save which works like the other claims and puts the code in your inventory
while this is planned it’s a lil hard for me to implement due to the fact that the way key codes work is associated w/ a purchase. allowing it to be just transferred with our current infra removes traceability. ideally we would have a new column w the new owner but still trace who it originally owned by, but then if that WERE the case, transferred keys would NOT be transferrable a second time (so only the original owner could’ve transferred it and it cant be transfered back) if that makes sense. tl;dr: not sure how to implement this well without a lot of effort
totally gotchu on this being a high workload! I think the lock system and list was alr a huge improvement to keys so /pos
for multiple transfers, would it be possible to overwrite the second column? assuming the most important data is just the og purchaser.
tbh tho, in my experience one transfer would absolutely be appreciated and cover a majority of use cases! if someone needs to transfer more, they can just use the “basic” system of unlocking and pasting lol.