Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rust crate bevy_renet to 0.0.12 #16

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2022

This PR contains the following updates:

Package Type Update Change
bevy_renet dependencies patch 0.0.5 -> 0.0.12

Release Notes

lucaspoffo/renet (bevy_renet)

v0.0.12

Compare Source

This release comes with 3 major changes:

  • Rewrite of the reliability/fragmentation protocol, it should handle any bandwidth.
  • Split of renet and the transport layer. Now its possible to use others transport protocols.
  • Configuration simplification
Renet
Added ⭐
  • Added NetcodeServer and NetcodeClient all the network transport logic has been moved to these structs.
    • You can check the documentation, examples, or demos to see how these new structs are used.
Changed 🛠️
  • Replaced RenetConnectionConfig with ConnectionConfig, this new configuration has been greatly simplified. You only need to specify how many bytes you can use per update tick and the channels configuration (ChannelConfiguration).
  • Rework of ChannelConfiguration, only 3 fields now: channel_id, max_memory_usage_bytes, and send_type.
  • RenetServer::newand RenetClient::new now only has ConnectionConfig as argument.
  • Renamed RenetServer::is_client_connected to is_connected.
  • NetworkInfo has bytes_sent_per_second and bytes_received_per_second instead of sent_kbps and received_kbps.
Removed 🔥
  • Removed send_packets from RenetServer and RenetClient, this is now done by the transport layer.
  • Removed can_send_message, this could cause some bad practices of checking before sending messages. If you cannot send a message you should change the channels configurations.
Rechannel

Rechannel has been deprecrated, all its logic has been moved inside renet.

Bevy Renet
Added ⭐
  • Added new Plugins for the transport layer: NetcodeServerPlugin and NetcodeClientPlugin.
  • Client disconnects when the app closes.
  • Server disconnects all clients when the app closes.
Changed 🛠️
  • Removed the clear_events options, you can achieve the same functionality by adding the Events yourself before the Plugin.

v0.0.11

Compare Source

Added ⭐
  • BevyRenet: updated bevy to version 0.10. (PR) by Shatur
  • RenetVisualizer: updated to egui 0.21.
  • Renet, Renetcode, BevyRenet: add client.is_connecting(). (commit)
  • Renet: allow to send empty messages again, this was a bad change since some serialization methods can serialize to empty messages. (commit)
Changed 🛠️
  • Renetcode: rename client.connected() with client.is_connected() for consistency. (commit)
Contributors 🙏

v0.0.10

Compare Source

Added ⭐
  • Added function client_addr, user_data, is_client_connected, max_clients, connected_clients for RenetServer, some utilities from NetcodeServer. (commit) (commit)
  • Renetcode/Renet: make generate_random_bytes public, this can be used to generate a random private key. (commit)
  • Rechannel: add DefaultChannel enum, usefull when using the default channel configuration. (commit)
  • BevyRenet: add configurable event clearing. (PR)
  • Rechannel: add configuration for unordered reliable channel. (commit)
  • Rechannel: add configuration for sequenced unreliable channel. (commit)
  • Renetcode: added logging. (commit) (commit)
  • BevyRenet: updated bevy to version 0.9; (PR)
Changed 🛠️
  • Renetcode: remove client_id argument when creating an RenetClient. (commit)
  • Rechannel: rename block channel to chunk channel, this makes clear what the channel does: the message is sliced in multiple chunks so it can be sent in multiple frames. Also, it is not confused with "blocking" thread/logic.
Fixed 🐛
  • Rechannel: when sending an empty message, this now gives an error. (commit)
  • Rechannel: ignore already received block messages. (commit)
Contributors 🙏

v0.0.9

Added ⭐
  • Rechannel: added max_message_size configuration for channels. This also fixes an exploit over the block channel,
    it was possible to send a SliceMessage with a high value of number of slices, this would cause the channel to allocate a lot of memory causing out of memories errors. (commit)
  • Rechannel: add fuzzing testing for processing packets (commit)
  • Add Secure/Unsecure option when creating the server/client, easier for testing or prototyping. (commit)
Changed 🛠️
  • Genericify send/recv methods, use Into<u8> for channel id and Into<Bytes> for messages (#​28)
  • Rechannel: split channels into Sender Channels and Receiver Channels. Now server and clients can have different channels (commit)
Fixed 🐛
  • Rechannel: fix block messages not correctly getting acked (commit)
  • Rechannel: check chunk id when receiving block messages (commit)
  • Rechannel: don't initialize block messages with 0 slices. Malformed packets could crash the server/client with out of bounds accesses (commit)
  • Rechannel: don't ack fragment packet on the first received fragment, only when all fragments are received (commit)
Removed 🔥
  • Removed renet::ChannelNetworkInfo (commit)
Contributors 🙏

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch 2 times, most recently from 5579f46 to 7da5aa8 Compare January 8, 2023 15:49
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch from d01caa7 to f04d4ad Compare March 12, 2023 08:18
@renovate renovate bot changed the title Update Rust crate bevy_renet to 0.0.6 Update Rust crate bevy_renet to 0.0.7 Mar 12, 2023
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch from f04d4ad to d8ad2b9 Compare March 15, 2023 19:21
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch from d8ad2b9 to b2544eb Compare April 1, 2023 17:10
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch from b2544eb to 805b4ca Compare May 19, 2023 22:51
@renovate renovate bot changed the title Update Rust crate bevy_renet to 0.0.7 Update Rust crate bevy_renet to 0.0.8 May 19, 2023
@renovate renovate bot changed the title Update Rust crate bevy_renet to 0.0.8 Update Rust crate bevy_renet to 0.0.9 Jul 20, 2023
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch from 805b4ca to 0cb12a9 Compare July 20, 2023 03:49
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch 3 times, most recently from 6394139 to 979090c Compare November 2, 2023 02:09
@renovate renovate bot changed the title Update Rust crate bevy_renet to 0.0.9 Update Rust crate bevy_renet to 0.0.10 Nov 12, 2023
@renovate renovate bot changed the title Update Rust crate bevy_renet to 0.0.10 Update Rust crate bevy_renet to 0.0.11 Feb 21, 2024
@renovate renovate bot force-pushed the renovate/bevy_renet-0.x branch from cbc402c to 73df940 Compare July 20, 2024 19:26
@renovate renovate bot changed the title Update Rust crate bevy_renet to 0.0.11 Update Rust crate bevy_renet to 0.0.12 Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants