Ok I guess we are talking about the same idea here. Having one node that handles "connection" and a different note handling the course of the street.
I would only argue that a connection with only on road connected should be able to exist in order to create a dead end. But don't know if this would make sense for your specific gameplay.
I'm sorry I can't help you any further here, but maybe someone else will have an idea.
Sorry, down is a substring of download I don't get your point either?
I really love the creative title :)
Ok so if I understood correctly you want to have one Node(of type Path3D or Curve3D) that will be used to generate a street from a given staring point to a given end point. And a second type of Node that should be handling intersections of a road?
My initial idea would be to have a area3D note for the intersection node and a area3D node as the start/endpoint of the path.
Then using the area_entered signal in the intersection area to detect if a path start/end was connected...
I have no experience of how well all of this will work in an tool script but this would be my starting point.
PS: after thinking twice about it. Why would you want to have a distinct intersection node? I think simply having a start and a endpoint of a street that can be connected to a different start/end point of a different street (or even the same to make a circle) should be enough.
I don't get it... "D" is a complete different character than "d" is.
It's like wondering why "file1" is not opened when I typed in "file2".
Well I didn't found anything regarding this on GitHub. And to be honest I only find some german language articles about this speaking of an announcement that signal don't likes the idea enabling Chats with WhatsApp... so I assume this comes from Twitter.
Like I said turn it of by default so that only people who activity made the decision can be chat with WhatsApp. Also showing a hint in the chat that this account is not on a signal server should also not be that hard to implement.
No and that's why signal can decide on their own if they want to enable chat with other messager or not. Meta has no choice anymore.
Matrix shows me that you can have both secure and decentralized communication.
Plus this refusal to allowing Chats to Whatsapp and Facebook Messenger now that EU forced meta to open this up...
I know the devs are not happy about meta tracking everything on their end but why can't this be a users choice to enable communication with no-signal servers as well?
IDK I thought sandboxing is also something that comes with Flatpak, so security concernes could be a reason to use Flatpak as well.
Birdo is that you?
Ah yes. I think I oversaw it. Personally I think this is not a big deal but people not very familiar with editing config files in editors maybe are afraid of doing this.
I mean the workaround would be to have something like a Array defined as an export variable and "drag and drop" the nodes you want to connect in the inspector?
But I think you already had something like this in place?