Cubby Posted July 11, 2022 Posted July 11, 2022 Bug Type (Server:): MCS Severity level (1-3): 2 Evidence (if you can): Go on the server and try Description of the bug: The way 332nd works right now is that it must be in the prefix of the name, however with either A) Set prefixes or B) A character limit on prefixes (idk how it works), It is impossible to add a regiment after 332nd. For example Johnpickels became 332nd and is SUPO, however it can't be added to the prefix because "33nd SUPO" doesn't work. You can enter it but you can't click the Green Check thingy. This could also be an issue for others whose prefix is just too long to actually be added. Again not sure if the prefix runs on a character limit, or only has a set list of items it accepts. How can we recreate it: Go on the server Note: I know there's been a lot of Bug reports, so if this already is done please forgive me, I checked and couldn't find it so. 1
Posted July 11, 2022 Bug Type (Server:): MCS Severity level (1-3): 2 Evidence (if you can): Go on the server and try Description of the bug: The way 332nd works right now is that it must be in the prefix of the name, however with either A) Set prefixes or B) A character limit on prefixes (idk how it works), It is impossible to add a regiment after 332nd. For example Johnpickels became 332nd and is SUPO, however it can't be added to the prefix because "33nd SUPO" doesn't work. You can enter it but you can't click the Green Check thingy. This could also be an issue for others whose prefix is just too long to actually be added. Again not sure if the prefix runs on a character limit, or only has a set list of items it accepts. How can we recreate it: Go on the server Note: I know there's been a lot of Bug reports, so if this already is done please forgive me, I checked and couldn't find it so. 1
Luther Posted July 11, 2022 Posted July 11, 2022 @CubbyAs of now you are not allowed to have spaces in your prefix. I don't know whether or not this is something that they are working on changing or not but that's why you can't have 332nd SUPO.
Posted July 11, 2022 @CubbyAs of now you are not allowed to have spaces in your prefix. I don't know whether or not this is something that they are working on changing or not but that's why you can't have 332nd SUPO.
Cubby Posted July 12, 2022 Author Posted July 12, 2022 Ah that makes sense, so it was intentional. Maybe server suggestion then
Founder Square Posted July 16, 2022 Founder Founder Posted July 16, 2022 This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS
Founder Founder Posted July 16, 2022 This has been marked as acknowledged and marked as a bug that is being looked into. This will remain unlocked in the case that more information becomes present. // MOVING TO ACKNOWLEDGED REPORTS
Baron Posted January 24, 2023 Posted January 24, 2023 This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
Posted January 24, 2023 This issue has been marked as resolved and therefore has been resolved on server or is unresolvable. // LOCKED // MOVED TO RESOLVED REPORTS
Recommended Posts