Burning Mesh 2025 userPrefs

MUI Boot logos courtesy of mentalconfection <3
This commit is contained in:
vidplace7
2025-06-30 22:51:58 -04:00
parent 86be2ac12f
commit 0dcd612a60
8 changed files with 20 additions and 18 deletions

View File

@@ -72,10 +72,11 @@ void FloodingRouter::perhapsRebroadcast(const meshtastic_MeshPacket *p)
tosend->hop_limit--; // bump down the hop count
#if USERPREFS_EVENT_MODE
if (tosend->hop_limit > 2) {
// BURNING MESH!
if (tosend->hop_limit > 3) {
// if we are "correcting" the hop_limit, "correct" the hop_start by the same amount to preserve hops away.
tosend->hop_start -= (tosend->hop_limit - 2);
tosend->hop_limit = 2;
tosend->hop_start -= (tosend->hop_limit - 3);
tosend->hop_limit = 3;
}
#endif
tosend->next_hop = NO_NEXT_HOP_PREFERENCE; // this should already be the case, but just in case

View File

@@ -38,7 +38,8 @@ enum RxSource {
#define HOP_MAX 7
/// We normally just use max 3 hops for sending reliable messages
#define HOP_RELIABLE 3
// BURNING MESH!
#define HOP_RELIABLE 4
// For old firmware or when falling back to flooding, there is no next-hop preference
#define NO_NEXT_HOP_PREFERENCE 0