Well you could always try attracting a Tech mod’s attention (they are always busy, so PMs are often missed) on the forms and pointing them that way. especially if they haven’t been touched in a while. Getting them actioned is a separate matter, which we’ve got no control over The “FIM-92 Overhaul” reports have been accepted for almost two years at this point, with no obvious corrective steps taken so far.
For example, I’d use the following to mention them as a “group”;
@Technical Moderators
or
" “@” Forum Moderators ", which gives actually gives me an error code “422”
But it’s (probably) bugged to not work I think since it contains “space”, a non-printing character which terminates the string, a “classic” character sanitization coding blunder, And the forums doesn’t have a separate reporting portal for issues so its never actually been functional, or reported.
The easiest way to fix this with limited “under the hood coding” would be to replace the space with either a hyphen or underscore to preserve the space with a “printed” character.
Since if you compare “@moderators” which as can be seen (at least in the editor), it looks a little different, and semi-functional.
Fair enough. So, for any @moderators that happen to take a look at this thread, i’ll just try to save some of your time by linking to the unreviewed bug reports below:
Some issues are more important than others, but if they are put on the cue alongside the already accepted reports like the F-106A missing the proper gunsight/3rd person view eggs, or the F-106 being able to fire the missiles in pairs that would be nice.
it was obvious when they misenterpreted the sources there was not much we could do about getting stingers buffed, you did an amazing job with the bugreport(you really shouldnt have had to do all that work as they were given primary sources) but its gaijin.