Wormholes

Yes, sorry it is a limitation of the EVE API. Until I develop a way to pull all characters and corporations into Tripwire OR CCP push CREST development further it is all I can do.

I meant to ask you before. What does the "favorite" button do. I have a system marked as a favorite and if I check the icon for "show favorite system in map" but it never shows up along side my home system

"Free - for a limited time!"

Wait. What?

AH. OK. Thanks for being open about it.

First, your forum appears to be broken. I cannot register because the capcha there with the registration code does not work. So I am posting this here instead.

I have been using tripwire a fair amount, and it is certainly a nice piece of software. However, it does require significant extra work to use, enough so that it is of borderline utility for me.

Let me step back and explain my situation. I have a small corp. We live in C4. Of us, only two are very active right now. I am one. The other seems to like Tripwire too. Several more log in just to do PVE and maybe get in on a gang if we happen to find someone to kill. All of us will work to find routes in/out for doing logistics. However the less active guys don't get anything from Tripwire except extra work. They don't use it that I know of.

My personal use of tripwire is largely for hunting. It means I can revisit systems I scanned last night and not have to scan as much. However, this is somewhat marginal. It is useful on the weekends (when I do revisit hours later or the next day), and not so much on weekdays. It would be a lot more useful if I could more freely mark systems. As it is, to get things marked up correctly requires significant extra labor for me.

One more bit of background to help you understand what I'd like to see. My corp "names" systems we find temporarily, for the one day we are attached to them. Our scheme starts with the wspace level -- i.e. C4, and appends 'a', 'b', 'c', etc. so as to uniquely name each system. So our home system is "C4a", our neighboring C4 through our static is "C4b", and etc. for later C4s we find. Nullsec is "ns", and there are "ls" and "hs".

We find this sort of naming to be very convenient. The particular J-names of systems are not helpful at all, because (a) they are too long, and (b) what matters to us is not the system per se but its position relative to us in the particular chain we have that day. I don't mind having the J-name there other than that it wastes space. I just don't use it. And that is one reason why using tripwire is work: because it records the names of systems as the J-name, and I don't.

So, what I would like is to have one more field in tripwire's data that it records for a wormhole. That field should be free form text entry, and it is my name for the system where the wormhole goes. For my purposes, it is sufficient that it be 3 characters. Others might want more. It can be left blank; if so, then tripwire does exactly what it does now. If it is not blank, then it becomes a second name for that system for the duration of my existing connection to it.

The primary purpose of this info would be to show it in the tree view of the chain. It could replace either the top label (where it currently shows "C4", "HS", etc.), or the J-name. Again: to me the J-name is completely irrelevant except insofar as I need it to get the thing to work right.

A secondary purpose for the label is to record the other side of a wormhole (since I can see it) in tripwire, when I see it.

One can tell via info box and eyeball what level wspace (or kspace) a wormhole goes to without going through. This is a second place where being able to free-text label a wormhole would be very helpful. When I scan down a system, I fly to each wormhole as I find it, and bookmark it, using our naming scheme. I.e., our static C4 wormhole is "Wormhole C4a->C4b" in my bookmarks, and that is before I have transited it. Because you want to fully scan a system before checking out wormholes, you end up with many bookmarked wormholes you have not transited yet. In tripwire you end up with a lot of K162s that have no known endpoint, and so you cannot tell them apart except that their signature tags are different. Needless to say, signature tags are extremely unhelpful as identifiers.

The tertiary use for the label is automapping. It is not helpful when automap asks me to pick a wormhole by its tag. I don't know the tags! Show me the name I entered, and I can pick right almost every time. Because in my mind I was heading into "C3a" to look around; I was not heading "to that wormhole with tag XYZ".

Also, if I have entered that a K162 goes to "C4c", then when I traverse a wormhole (tripwire does not know which one, of course), and I end up in a C4 that is not yet mapped, then I want tripwire to automap accordingly. If there are multiple wormholes that I have noted as going to C4, then sure, have me disambiguate. But only them.

Here are a few other small things that I'd like.

First, instead of "???", just put one "?". One gets the point across, and is is easier to highlight. (Double-click seems to just get one char.)

Second, what I really want to know about the static wormholes per system (which you display in the system info), is not what you display. I know all the wormhole mass limits and lifetimes by heart, and/or they usually don't matter anyway. What I do not know is their signature strength, and yet that is the one thing I need to know to search for them. Please add this info.

If the diversity of methods is the problem why not just let us assign and edit our own designations even if not automactic? E.g. C3a, C3b, C3c, C3-Fred etc.

I'd like to try this tool out. Can my corp get access please?

Another day, another Tripwire update with some fixes and back-end changes..

• EVE API optimizations and error handling (thanks to all these DDoS attacks)
• More log-in fixes and improvements (mostly back-end)

Also there seems to be some confusion... please be sure you are using Tripwire now... not Galileo. Galileo is the test version that I work on and break.

Tripwire:
https://tripwire.cloud-things.com

Galileo:
https://galileo.tripwire.cloud-things.com

Been testing this for a while. Great tool.

A couple of comments / improvements.

- When you switch system there is a noticable 2 sec refresh while the entire page reloads. In contrast to siggy where its a smooth transisition. I suspect because you reload the background picture each time where perhaps siggy just updates the postion graphic. Be great if you could fix that as will make fast switching between systems much easier.

EDIT - noticed its the galileo version that reloads the background graphic. However the regular version still has the 1-2 sec refresh (its quicker than galileo though) Note. i live in Australia so that might be impacting my load times.

- Be good to have the static and evekill/dotlan information on the top of the box (above the api graph). Reason - this would allow users to resize the box to be smaller thus enabling a larger chain map. Cause currently if you resize the graph box to be smaller you hide the static/kill info.

- a link to zkillboard would be nice. Eve-Kill tends to be 30-40mins behind zkillboard with the kill updates.

- In the sig section. Be nice to have the option to put leads to low sec ; null sec ;high sec etc. rather than having to specify the system. because sometimes you dont want to jump through but still want to let your corp mates know that there is a K to null in that system etc

- also nice if the sigs wouldnt appear in the chain map until you actually jump through them. but thats just personal preference. Cause currently i mark something as K162 and it appears in the map. but then i jump through that WH and a 2nd connection appears in the chain map. When really there is only one connection.

I have released another minor tweak & bugfix patch.

Things you might notice...

• Animations should play smoother
• Added a Donate button at the bottom - money goes to pay for servers
• Background scaling change to work better