The one feature Siggy has vs Tripwire
I love tripwire, it's gorgeous and easy to use. Siggy feels like some sort of ancient incarnation of this, however for us K-Space residents siggy has one thing tripwire does not: The ability to connect k to k systems so we can easily see wormholes of nearby systems without having to load up that system on the webpage or go to that system personally.
This seems like a simple option to add and I would love to see it.
Comments (16)
-
repo owner -
reporter Oh nice, this should work for now. Do the fake sigs get auto deleted when pasting new stuff and choosing the "delete non-existant sigs" option?
-
repo owner Nope, there is a check that prevents the "GATE" types from being deleted when using that feature. :)
-
repo owner No, there is a check to skip those types when deleting
-
reporter Wow, that's really awesome. I think this is nearly perfect. Thanks :)
-
repo owner Sweet, looks like an email reply does update the tickets - takes awhile though. (that is why I doubled answered)
Still got tons of features to add but it does work quite well when you learn how to fully use it. Still need to get documentation and tutorials built into it too obviously lol.
-
reporter Only thing that is sort of annoying (and really the only "problem" I have with this work around thusfar) is having to make up sig names. I'm using things like AAA, AAB, AAC etc... for now.
-
repo owner ??? Is allowed as a signature id
-
reporter Just found a problem. It seems like gate signatures do get deleted only because they become "K162" after people move through them with tripwire open. I have all my gate connections labeled "GATE" as their type but when I jump through them they become "K162" which can be auto-deleted.
-
repo owner Interesting, something I should be able to fix tomorrow then.
-
It has always set these up as GATE-K162 for me. If you update the K162 end to GATE, the original end becomes K162, so you can't set up a GATE-GATE connection.
Also, while ??? is allowed as an ID, you can't add more than one ??? manually (Signature ID already exists!)
-
repo owner I am actually working on fixing that and several other issues related to using GATE as signatures. I am testing the changes right now on Galileo and should be pushed live to Tripwire very soon.
-
repo owner Patch released - let me know if that makes your life a bit better
-
Confirming I now have GATE connections aged over 100 hours.
-
repo owner - changed status to resolved
-
repo owner - removed version
Removing version: 0.Next (automated comment)
- Log in to comment
I did add a work-around for this in Tripwire. Create fake wormholes and use the wormhole type of "GATE" instead of say "B274". This provides an infinite wormhole that has a gray line in the chain map.