RiptideNetworking/Riptide issues and pull requests

#160 - Compact message data

Pull Request - State: closed - Opened by Per6 about 1 month ago - 3 comments
Labels: Won't Fix

#159 - Disconnected from server: Poor connection.

Issue - State: open - Opened by mblogest about 1 month ago - 1 comment

#158 - Use Message.Create to send disconnect message on server stop

Pull Request - State: closed - Opened by apkatsikas about 1 month ago
Labels: Bug

#157 - Running Server.Stop() does not result in Client getting expected Disconnect Reason

Issue - State: closed - Opened by apkatsikas about 1 month ago - 1 comment
Labels: Bug

#156 - add nanosockets

Pull Request - State: open - Opened by Molth about 2 months ago

#155 - Feature Request: Encryption/Decryption Support for Network Traffic

Issue - State: open - Opened by snnaakee about 2 months ago - 5 comments
Labels: Feature Request, Under Consideration

#154 - Not supported on .NET Framework 3.5

Issue - State: closed - Opened by NetheriteOfficial about 2 months ago - 3 comments
Labels: Feature Request, Won't Fix

#153 - Could not guarantee delivery of a ClientConnected message after 15 attempts! Disconnecting..

Issue - State: closed - Opened by GatitoStudio 2 months ago - 2 comments
Labels: User Error, Question

#152 - Feature Request: New Send mode with even better reliability

Issue - State: closed - Opened by Per6 2 months ago - 2 comments
Labels: Feature Request, Won't Fix

#151 - Messages become unusable for no reason

Issue - State: closed - Opened by Per6 2 months ago - 4 comments
Labels: User Error

#150 - Overly reliable send mode and Id parameter for messages

Pull Request - State: closed - Opened by Per6 2 months ago - 12 comments
Labels: Feature Request, Won't Fix

#149 - Feature Request: Reliable messages with backup

Issue - State: closed - Opened by Per6 2 months ago - 1 comment

#148 - when writing and reading a line the first character is lost

Issue - State: closed - Opened by IKatyrov 2 months ago - 1 comment
Labels: User Error

#147 - Feature Request: Allow host names in addition to ip-addresses

Issue - State: open - Opened by Jeroen-R 3 months ago - 5 comments
Labels: Feature Request, Under Consideration

#146 - Feature request: For Server, allow the IP Address to be specified

Issue - State: closed - Opened by Jeroen-R 3 months ago - 1 comment
Labels: Feature Request, Already Exists

#145 - (SERVER): Could not guarantee delivery of a Welcome message after 15 attempts! Disconnecting...

Issue - State: closed - Opened by NetheriteOfficial 3 months ago - 5 comments
Labels: User Error

#144 - Throw exception when failing to read from message.

Issue - State: open - Opened by titusio 4 months ago - 2 comments
Labels: Feature Request

#144 - Throw exception when failing to read from message.

Issue - State: open - Opened by titusio 4 months ago - 2 comments
Labels: Feature Request

#143 - Can you upgrade ushort client ids to 32 bit unsigned integers ?

Issue - State: closed - Opened by CrossV4 4 months ago - 2 comments
Labels: Feature Request, Won't Fix

#142 - Kcp Transport

Issue - State: closed - Opened by coinsoundsbetter 4 months ago - 1 comment
Labels: Feature Request, Question, Under Consideration

#141 - Switch to nanosockets to minimize allocations

Issue - State: open - Opened by megalithos 6 months ago - 1 comment
Labels: Feature Request

#141 - Switch to nanosockets to minimize allocations

Issue - State: open - Opened by megalithos 6 months ago - 1 comment
Labels: Feature Request

#140 - MessageExtensionUnity.cs missing in Repo

Issue - State: closed - Opened by ApfelTeeSaft 6 months ago - 1 comment
Labels: User Error, Question

#140 - MessageExtensionUnity.cs missing in Repo

Issue - State: closed - Opened by ApfelTeeSaft 6 months ago - 1 comment
Labels: User Error, Question

#139 - PlayerLeft event Hook in NetworkManager not working

Issue - State: closed - Opened by ApfelTeeSaft 6 months ago - 1 comment
Labels: User Error

#139 - PlayerLeft event Hook in NetworkManager not working

Issue - State: closed - Opened by ApfelTeeSaft 6 months ago - 1 comment
Labels: User Error

#138 - Seperate server and client library

Issue - State: closed - Opened by bberka 7 months ago - 1 comment
Labels: More Info Required

#138 - Seperate server and client library

Issue - State: closed - Opened by bberka 7 months ago - 1 comment
Labels: More Info Required

#137 - Better packet model handling

Issue - State: closed - Opened by bberka 7 months ago - 1 comment
Labels: Feature Request, Already Exists

#137 - Better packet model handling

Issue - State: closed - Opened by bberka 7 months ago - 1 comment
Labels: Feature Request, Already Exists

#136 - Change Id method

Issue - State: closed - Opened by Per6 8 months ago - 2 comments
Labels: Feature Request, Already Exists

#136 - Change Id method

Issue - State: closed - Opened by Per6 8 months ago - 2 comments
Labels: Feature Request, Already Exists

#135 - Reliability of reliable messages

Issue - State: closed - Opened by Per6 8 months ago - 2 comments
Labels: Question

#135 - Reliability of reliable messages

Issue - State: closed - Opened by Per6 8 months ago - 2 comments
Labels: Question

#134 - Simulating network conditions (latency/ping, packet loss, etc.)

Issue - State: open - Opened by devilExE3 9 months ago - 2 comments
Labels: Feature Request, Question, Won't Fix

#134 - Simulating network conditions (latency/ping, packet loss, etc.)

Issue - State: open - Opened by devilExE3 9 months ago - 2 comments
Labels: Feature Request, Question, Won't Fix

#133 - [Bug/Question] UnreadBits not zero after reading all data from Notify message

Issue - State: closed - Opened by Charanor 9 months ago - 3 comments
Labels: Question

#133 - [Bug/Question] UnreadBits not zero after reading all data from Notify message

Issue - State: closed - Opened by Charanor 9 months ago - 3 comments
Labels: Question

#132 - [Bug] Some values not being read properly

Issue - State: closed - Opened by Charanor 9 months ago - 2 comments
Labels: User Error

#132 - [Bug] Some values not being read properly

Issue - State: closed - Opened by Charanor 9 months ago - 2 comments
Labels: User Error

#131 - [Question] Example usage of Notify send mode?

Issue - State: closed - Opened by Charanor 10 months ago - 7 comments
Labels: Question

#131 - [Question] Example usage of Notify send mode?

Issue - State: closed - Opened by Charanor 10 months ago - 7 comments
Labels: Question

#130 - Fix ack message sending redundant sequence ID

Pull Request - State: closed - Opened by RudyTheDev 11 months ago
Labels: Bug

#130 - Fix ack message sending redundant sequence ID

Pull Request - State: closed - Opened by RudyTheDev 11 months ago
Labels: Bug

#129 - Show message id when reliable message fails to ack in PendingMessage.TrySend

Issue - State: open - Opened by jwlondon98 11 months ago - 1 comment
Labels: Feature Request, Under Consideration

#129 - Show message id when reliable message fails to ack in PendingMessage.TrySend

Issue - State: open - Opened by jwlondon98 11 months ago - 1 comment
Labels: Feature Request, Under Consideration

#128 - Suggestion for AddBytes method

Issue - State: closed - Opened by megalithos 11 months ago - 1 comment
Labels: Feature Request

#128 - Suggestion for AddBytes method

Issue - State: closed - Opened by megalithos 11 months ago - 1 comment
Labels: Feature Request

#127 - Added overload Get methods with only array no set amount to Message, also Fixed spelling mistake.

Pull Request - State: closed - Opened by Gohan500 11 months ago

#127 - Added overload Get methods with only array no set amount to Message, also Fixed spelling mistake.

Pull Request - State: closed - Opened by Gohan500 11 months ago

#126 - update

Pull Request - State: closed - Opened by Gohan500 11 months ago - 4 comments

#126 - update

Pull Request - State: closed - Opened by Gohan500 11 months ago - 4 comments

#125 - Client _._._._:_ stopped responding while the connection was fully established!

Issue - State: closed - Opened by minhtribui153 11 months ago - 4 comments
Labels: User Error

#125 - Client _._._._:_ stopped responding while the connection was fully established!

Issue - State: closed - Opened by minhtribui153 11 months ago - 4 comments
Labels: User Error

#124 - Serialisation Bug

Issue - State: closed - Opened by eeetem 11 months ago - 1 comment
Labels: Bug

#124 - Serialisation Bug

Issue - State: closed - Opened by eeetem 11 months ago - 1 comment
Labels: Bug

#123 - The second client to connect is disconnected because a reliable message can't be delivered

Issue - State: closed - Opened by tom-weiland 12 months ago
Labels: Bug

#123 - The second client to connect is disconnected because a reliable message can't be delivered

Issue - State: closed - Opened by tom-weiland 12 months ago
Labels: Bug

#122 - Fix minor typo in send modes explaination

Pull Request - State: closed - Opened by Mograine 12 months ago - 2 comments
Labels: Documentation

#122 - Fix minor typo in send modes explaination

Pull Request - State: closed - Opened by Mograine 12 months ago - 2 comments
Labels: Documentation

#121 - Reworked the Message class to operate on the bit level (as opposed to the byte leve)

Pull Request - State: closed - Opened by tom-weiland 12 months ago

#121 - Reworked the Message class to operate on the bit level (as opposed to the byte leve)

Pull Request - State: closed - Opened by tom-weiland 12 months ago

#120 - dose it work on sanctioned countrys

Issue - State: closed - Opened by mostafablender about 1 year ago - 1 comment
Labels: Question

#119 - Bug | Eating bytes if is count more than 32767 (Message only contains 7170 unread bytes, which is not enough to retrieve 72706 bytes! Returned array will contain default elements)

Issue - State: closed - Opened by DPrison about 1 year ago - 2 comments
Labels: Bug, Already Exists

GitHub / RiptideNetworking/Riptide issues and pull requests