-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Plasma station should not have radioactive suppermatter item. #34710
Comments
so what is the specific issue. does it feel as if it isn't communicated well? is it the fact that you can eat the radioactive? because to me it was obvioustly radioactive (radiation collector is right there. it has to be there for a rason). and since i knew it was radioactive I knew I shouldn't eat it. |
or is it that it is a map-specific prototype? |
fixed by #34726 |
no mald prs |
I found it lying around a hallway because somebody moved it. I picked it up knowing it is a completely benign (if funny) food item, then suddenly collapsed 2 minutes later and was unrevivable. Even if I'd found it around the rad collector I would assume it is a funny joke and that it's not actually radioactive. If we really wanted to keep this as radioactive I think it should at least need a distinct sprite. |
In the future it would probably be a good idea to make it possible to tell if you're taking radiation damage, there's already an open issue on this edit: wrong link |
thats the idiffrence. because I didn't know that a small supermatter chunk was non-radioactive. all I saw was a emitter and a radiation collector. so I assumed it was radioactive (shortly before missing the movement and drifting off into space forgetting I can throw stuff to head back to station) |
Hi. I just died to this. We should not teach players that a normal food item is radioactive. The subtle change in name and item description is not enough to distinguish this, not to mention that any such changes really should be a proper prototype instead of a map hack like this.
The text was updated successfully, but these errors were encountered: