Allow unverified users to access /filter, but still blocking comman…

…ds (#625)

If a user is playing on an unverified account, they wont be able to edit
text in magic mouths on their moon right now, which is definitely not
the intended behaviour.

So we allow unverified `/filter` requests, but block commands from being
run.

Refresh.GameServer/Endpoints/Game/ModerationEndpoints.cs

@@ -43,7 +43,6 @@ public SerializedModeratedResourceList ModerateResources(RequestContext context,
     /// <param name="database">The database. Used for commands</param>
     /// <returns>The string shown in-game.</returns>
     [GameEndpoint("filter", HttpMethods.Post)]
-    [RequireEmailVerified]
     [AllowEmptyBody]
     public string Filter(RequestContext context, CommandService commandService, string body, GameUser user, Token token, GameDatabaseContext database)
     {
@@ -67,8 +66,8 @@ public string Filter(RequestContext context, CommandService commandService, stri
         {
             context.Logger.LogInfo(BunkumCategory.Filter, $"<{user}>: {body}");
 
-            //If the text starts with a `/`, its a command
-            if (body.StartsWith('/'))
+            //If the text starts with a `/`, its a command, also only allow verified users to use commands
+            if (body.StartsWith('/') && user.EmailAddressVerified)
             {
                 try
                 {