-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supermatter shards don't arrive with a crate #7994
Comments
also if it helps for issue reproduction, this was off of the guild departmental account. |
Adding a warning for carts with high risk items would probably help. |
Maybe we should change the SM to not dust people, just burn + irradiate them. SM dusting almost isn't ever a fun mechanic even for traitors, getting round removed because you misclicked or lagged isn't ever fun. |
This is a terrible idea. SM dusting is the best shit ever and I want my SM disposal chute I build round start to enable me to make a vagabond powered ship until I reroute all trash bins to point at the SM. Trash ship is a good ship. |
We should make the SM dust not only on contact but if you are thrown into it as well (iirc it doesnt rn) |
Per issue discordia-space#7994, quick check for SM shard and crates the order if SM is present in order
Tested manually throwing a person into the SM, dusting works in that case. Might be a issue when thrown by a device ie disposals |
* SM now comes in crates Per issue #7994, quick check for SM shard and crates the order if SM is present in order * Fix for always true find() returns 0 if item is not found, not -1 apparently --------- Co-authored-by: Eugene Shih <[email protected]>
so as it currently stands, ordering an SM shard from guild, for 12000 sends an entire shard, without a crate.
if someone doesn't know how an SM works by activation from a single dusting, this can slightly derail or end an entire round also its nearly impossible to move out of the guild, due to this.
there isn't any warning on the order menu for this, so I'm presuming its unintentional.
The text was updated successfully, but these errors were encountered: