From 7c341e4e8991d1847f4e8950e666746627e70d6e Mon Sep 17 00:00:00 2001 From: Chris Langsenkamp Date: Mon, 23 Sep 2019 00:08:41 -0400 Subject: [PATCH] removed redundant bullet point --- doc/Guides/Authentication.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/Guides/Authentication.md b/doc/Guides/Authentication.md index 490a441d5..d69d4ede4 100644 --- a/doc/Guides/Authentication.md +++ b/doc/Guides/Authentication.md @@ -49,7 +49,6 @@ To make your own custom Authenticator, you can just create a new script in your Here are some tips for custom Authenticators: - `OnStartServer` and `OnStartClient` are the appropriate methods to register server and client messages and their handlers. They're called from StartServer/StartHost, and StartClient, respectively. -- `RegisterMessage` has a boolean parameter `requireAuthentication`. This defaults to true and **must** be specified false for any messages you need to exchange with the client before they're authenticated. - Send a message to the client if authentication fails, especially if there's some issue they can resolve. - Call the `Disconnect()` method of the `NetworkConnection` on the server and client when authentication fails. If you want to give the user a few tries to get their credentials right, you certainly can, but Mirror will not do the disconnect for you. - Remember to put a small delay on the Disconnect call on the server if you send a failure message so that it has a chance to be delivered before the connection is dropped.