• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 Hive's 6th HD Modeling Contest: Mechanical is now open! Design and model a mechanical creature, mechanized animal, a futuristic robotic being, or anything else your imagination can tinker with! 📅 Submissions close on June 30, 2024. Don't miss this opportunity to let your creativity shine! Enter now and show us your mechanical masterpiece! 🔗 Click here to enter!

Maps in folders with # in the file path break some pathability rules and can desync

Status
Not open for further replies.
Level 39
Joined
Feb 27, 2007
Messages
5,034
Maybe the OP posted again but if they didn't here's an attempt to gain visibility: What is "path component index out of bounds" fatal error?

Absolutely sure! Put # in folder name, you can now build on path and will consistently crash if you play with other people, remove # and all is fixed. Works with Pumpkin TD and Blacksmith TD so far, probably triggers all kinds of interesting bugs in other maps.

MQhW54Vm.png


xqLgM3Qm.png


Edit: Tried a few maps, works in most TDs

wRAnc16m.png


Hahaha

K0gYcQd.jpg
Sorry for the necropost, but I just found this thread today and decided to do some testing with it for multiplayer. Here are my findings:

When the host hosts the map from # folder, if the other players that join the lobby also have the map in a # folder, no one desyncs. If the other players DON'T have the map in a # folder, they will desync.

When I hosted my map from a normal non-# folder, I had the other tester join with the map in a # folder on his end, and it did not prompt a re-download, and I was the one that desynced. He still stayed in the map.
@GrapesOfWath
 
Status
Not open for further replies.
Top