Jump to content

Suchdiffrent

Members
  • Posts

    3
  • Joined

  • Last visited

Suchdiffrent's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Good afternoon, I'm trying to configure Velocity and Forge 1.16.5, but there is a problem: I get kicked with this error: [14:43:51] [Netty Epoll Server IO #1/ERROR] [ne.mi.fm.ne.NetworkRegistry/NETREGISTRY]: Channels [hc:hollow_core_channel] rejected vanilla connections [14:43:51] [Netty Epoll Server IO #1/INFO] [ne.mi.fm.se.ServerLifecycleHooks/SERVERHOOKS]: Disconnecting VANILLA connection attempt: This server has mods that require Forge to be installed on the client. Contact your server admin for more details. I have installed one mod, self-written. The version of the mod coincides completely. On a clean forge easily comes in. Client log: [14:46:19] [Netty Client IO #4/INFO]: Connected to a vanilla server. Catching up missing behaviour. [14:47:03] [Render thread/INFO]: Connecting to 135.181.6.59, 25566 velocity.toml # Config version. Do not change this config-version = "1.0" # What port should the proxy be bound to? By default, we'll bind to all addresses on port 25577. bind = "0.0.0.0:25565" # What should be the MOTD? This gets displayed when the player adds your server to # their server list. Legacy color codes and JSON are accepted. motd = "&#09add3A Velocity Server" # What should we display for the maximum number of players? (Velocity does not support a cap # on the number of players online.) show-max-players = 500 # Should we authenticate players with Mojang? By default, this is on. online-mode = false # If client's ISP/AS sent from this proxy is different from the one from Mojang's # authentication server, the player is kicked. This disallows some VPN and proxy # connections but is a weak form of protection. prevent-client-proxy-connections = false # Should we forward IP addresses and other data to backend servers? # Available options: # - "none": No forwarding will be done. All players will appear to be connecting # from the proxy and will have offline-mode UUIDs. # - "legacy": Forward player IPs and UUIDs in a BungeeCord-compatible format. Use this # if you run servers using Minecraft 1.12 or lower. # - "bungeeguard": Forward player IPs and UUIDs in a format supported by the BungeeGuard # plugin. Use this if you run servers using Minecraft 1.12 or lower, and are # unable to implement network level firewalling (on a shared host). # - "modern": Forward player IPs and UUIDs as part of the login process using # Velocity's native forwarding. Only applicable for Minecraft 1.13 or higher. player-info-forwarding-mode = "none" # If you are using modern or BungeeGuard IP forwarding, configure a unique secret here. forwarding-secret = "DqsrjyPN7mhB" # Announce whether or not your server supports Forge. If you run a modded server, we # suggest turning this on. # # If your network runs one modpack consistently, consider using ping-passthrough = "mods" # instead for a nicer display in the server list. announce-forge = true # If enabled (default is false) and the proxy is in online mode, Velocity will kick # any existing player who is online if a duplicate connection attempt is made. kick-existing-players = false # Should Velocity pass server list ping requests to a backend server? # Available options: # - "disabled": No pass-through will be done. The velocity.toml and server-icon.png # will determine the initial server list ping response. # - "mods": Passes only the mod list from your backend server into the response. # The first server in your try list (or forced host) with a mod list will be # used. If no backend servers can be contacted, Velocity won't display any # mod information. # - "description": Uses the description and mod list from the backend server. The first # server in the try (or forced host) list that responds is used for the # description and mod list. # - "all": Uses the backend server's response as the proxy response. The Velocity # configuration is used if no servers could be contacted. ping-passthrough = "mods" [servers] # Configure your servers here. Each key represents the server's name, and the value # represents the IP address of the server to connect to. lobby = "127.0.0.1:25566" # In what order we should try servers when a player logs in or is kicked from a server. try = ["lobby"] [forced-hosts] [advanced] # How large a Minecraft packet has to be before we compress it. Setting this to zero will # compress all packets, and setting it to -1 will disable compression entirely. compression-threshold = 256 # How much compression should be done (from 0-9). The default is -1, which uses the # default level of 6. compression-level = -1 # How fast (in milliseconds) are clients allowed to connect after the last connection? By # default, this is three seconds. Disable this by setting this to 0. login-ratelimit = 3000 # Specify a custom timeout for connection timeouts here. The default is five seconds. connection-timeout = 5000 # Specify a read timeout for connections here. The default is 30 seconds. read-timeout = 30000 # Enables compatibility with HAProxy's PROXY protocol. If you don't know what this is for, then # don't enable it. haproxy-protocol = false # Enables TCP fast open support on the proxy. Requires the proxy to run on Linux. tcp-fast-open = false # Enables BungeeCord plugin messaging channel support on Velocity. bungee-plugin-message-channel = true # Shows ping requests to the proxy from clients. show-ping-requests = false # By default, Velocity will attempt to gracefully handle situations where the user unexpectedly # loses connection to the server without an explicit disconnect message by attempting to fall the # user back, except in the case of read timeouts. BungeeCord will disconnect the user instead. You # can disable this setting to use the BungeeCord behavior. failover-on-unexpected-server-disconnect = true # Declares the proxy commands to 1.13+ clients. announce-proxy-commands = true # Enables the logging of commands log-command-executions = false [query] # Whether to enable responding to GameSpy 4 query responses or not. enabled = false # If query is enabled, on what port should the query protocol listen on? port = 25577 # This is the map name that is reported to the query services. map = "Velocity" show-plugins = false What could be the problem? How can I fix it?
  2. Hey! Now i can send packets from spigot server to client server. But if i want send packet to forgemod-server, i need first send packet to client, and then to server. How i can send packet from spigot-server to forgemod server without client? Spigot and forge mod on one vds.
  3. Hey! Is there any way to receive packets from spigot server to forge client? I saw this topic: https://mcforge.readthedocs.io/en/1.16.x/networking/simpleimpl/, but i think it's only forge client-forge mod communication. Version: 1.16.5
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.