Pages: 1 [2] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Nelly Uanos
Quebec's Underdog League Quebec United Legions
10
|
Posted - 2014.03.07 01:36:00 -
[31] - Quote
Well we do have other letter for the wormhole state or K162 in our BM
Could look like.
DC5 (Mean dead as EOL) MC5 (Mass been reduced) VC5 (Verge) KC5 (K162)
This can give result like that at worse...
DVKNS-2
About expired BM, well to really do it well you need to re-scout your chain and update it manually.
The only "trick" i use to speed up the process is usually delete any BM older than 24h. |
Bane Nucleus
Sky Fighters
1176
|
Posted - 2014.03.07 01:52:00 -
[32] - Quote
I love seeing the different ways people label stuff. We have come a long way from the days of using an excel spreadsheet to map hahaha No trolling please |
ARMED1
Merchants Trade Consortium The Last Chancers.
32
|
Posted - 2014.03.07 03:47:00 -
[33] - Quote
I just call them all "your mom" as I jump in and out of them at will...
|
Icarus Able
Revenant Tactical
363
|
Posted - 2014.03.07 04:34:00 -
[34] - Quote
C3 static is C3 Any hole in there is 1,2,3,4 or 5 etc. Then in 1 you name each wormhole ,11,12,13,14,15,16,17 This could get really confusing with a deep chain but we rarely go more than 4-5 jumps down. And Omega always leads to home.
Well this is the system we are supposed to use if everyone could bookmark correctly. |
Blodhgarm Dethahal
Transcendent Sedition Dustm3n
84
|
Posted - 2014.03.07 05:00:00 -
[35] - Quote
!XXX-WH ID-DESTINATION (###) STATUS
Ex. ABC-X877-C4 (123) EOL
Numbers only needed if there are multiple of same class in system. If needed numbers are last 3 of system name.
Status only needed if it is not healthy.
We probably don't need the sig ID however.. bad habit of mine from pre chain mapper days.. -Bl+¦d |
Bloemkoolsaus
Viperfleet Inc. Disavowed.
129
|
Posted - 2014.03.07 08:18:00 -
[36] - Quote
hydraSlav wrote:Although, i still can't imagine anyone navigating from one branch of the chain into another (for a CTA) without looking at the route on the mapper, and in that case, it shows you where you are anyways...
Well, we usually have more then 10 wormholes in our current connected chain. Imagine you are scanning with your scan alt somewhere in the chain, another scouts finds pewpew in a different part of the chain. Quickly look at the mapper where he is in relation to you. In the mean time, a fleet is formed in the home system wich you join with your main. You rush your own scan alt to the system, to have extra eyes while you move your main with the fleet from the home system. You now have to navigate 2 pilots, not only that, there is a lot of chatter on comms from the FC and scout, you have to keep up with fleet commands, and keep an eye on your scout for anything you see.
It's pretty easy to loose sight of where you currently are in situtaions like this
|
Lloyd Roses
Blue-Fire
535
|
Posted - 2014.03.07 10:02:00 -
[37] - Quote
Personally got many situations with alts having to map space without siggy/tripwire/similiar.
So it turned out to look like this:
1 c2 for the first c2 in line. Then -1 11 c4 12 c2 for outgoing holes from there... 1-1 111 c4 112 c5 and so on.
it only starts causing issues when the next hole looks like this: 3112.1244.1 c6 ... no system is perfect. "I honestly thought I was in lowsec"
Moving pictures |
Lilli Tane
Lead Farmers Kill It With Fire
10
|
Posted - 2014.03.07 14:51:00 -
[38] - Quote
There is way too few information on that systems, a good BM naming system need to: GÇóBe easy to read GÇóHave all the information needed GÇóBe easy to understand
There for I present you LTBMNMC5.0
Here is an example BM
0101J111111C5H296300015001230MSTSO
And the correspondent return BM
0001J222222C5K162300015001230MSTSR
This BM system supports: GÇóAll 5000 systems in eve, GÇóAll WH types, GÇóChains of 99 wormholes, GÇóMax mass allowance, GÇótime it was created, GÇóSolar systems with 99 wormholes, GÇóMax mass per jump, GÇóMass status, GÇóTime status, And it can be read at glance, and itGÇÖs easy to understand.
|
Blodhgarm Dethahal
Transcendent Sedition Dustm3n
84
|
Posted - 2014.03.07 18:25:00 -
[39] - Quote
Lilli Tane wrote:There is way too few information on that systems, a good BM naming system need to: GÇóBe easy to read GÇóHave all the information needed GÇóBe easy to understand
There for I present you LTBMNMC5.0
Here is an example BM
0101J111111C5H296300015001230MSTSO
And the correspondent return BM
0001J222222C5K162300015001230MSTSR
This BM system supports: GÇóAll 5000 systems in eve, GÇóAll WH types, GÇóChains of 99 wormholes, GÇóMax mass allowance, GÇótime it was created, GÇóSolar systems with 99 wormholes, GÇóMax mass per jump, GÇóMass status, GÇóTime status, And it can be read at glance, and itGÇÖs easy to understand.
Brilliant.. I will be immediately using this format.. 10/10
-Bl+¦d |
Kirasten
Sin Factory Infinite Anarchy
0
|
Posted - 2014.03.07 18:58:00 -
[40] - Quote
The important part is that each wh get it's own identity. It doesn't matter that much which of the methods posted you use. They all have the same common denominator. They all name each wh something different.
I kind of like the idea of K162 holes into our home system going reverse letter-wise (C5z, C5y, etc), but we don't do that. As long as they are named differently than the others, you can see where they are. The only time this will be confusing is if you DON'T use your corp/alliance's mapper. We make our bookmarks this way specifically so that people use their mapper. It is set as my home page, so one click and i can see a visual of the entire chain. That way it doesn't really matter what you call each hole.
If we named them "Icecream", "Tomato", and "Sea Bass", then when your FC says you have a fight in Tomato, you click your mapper, and see you need to look for the Icecream bm and then Tomato.
Easy.
We name our return bookmarks the same way. In the above example, if your scout said you had targets in Tomato and you were in Sea Bass, then you would just look for the Tomato bm. It doesn't matter which "direction" the wh is going.
P.S. We don't use names like Tomato, it was just an example of how what the names are, isn't that important. We just use the normal C5a. C5b, C3a, etc. |
|
Noxisia Arkana
Deadspace Knights
226
|
Posted - 2014.03.07 19:32:00 -
[41] - Quote
Will start using arbitrary names to start naming WH chains.
WhaleTail1 -> WhaleTail2 -> WhaleTail3 -> WhaleTail3b
Guys, we've got something in the whaletail chain! Everyone into the whaletail! |
XODIOS Katelo
Oath of the Forsaken Sanguis Ignis Prosperitum
0
|
Posted - 2014.03.07 20:06:00 -
[42] - Quote
We just name them class of system and the last three digits of the Jsig, ie C3 456 or something.
If it goes home, it's named "Home" or "Home via C4" ect
If it goes to Highsec or Lowsec it's named LS Tama or HS Amarr.
If it's anything too complex it's a pain for newer members without really giving much extra information. Everyone should have siggy open all the time anyway and Navigate using that.. |
Streya Jormagdnir
Alexylva Paradox
330
|
Posted - 2014.03.10 04:36:00 -
[43] - Quote
Our bookmarking convention revolves around being able to navigate back to our home system. Let's say you have a C5 static you call "Bacon". There could be any number of wormholes in Bacon, but we always consider Bacon's static to be the "first" wormhole. Any wormholes that aren't the return hole or the static are given an arbitrary number. So let's say today's Bacon has a C4 static and a K162 from fellow C5 space. The C4 would be called Bacon-1 and the C5 would be called Bacon-2, and the bookmarks would look like:
Bacon-1 (C4S)[SIG] and Bacon-2 (C5i)[SIG]
Where "S" indicates a static, "i" indicates a K162 (inbound) and "o" would indicate an outbound wandering. With such a system we navigate however far down or across chain we want, and end up with some long names such as Bacon-1.2.1.6 (to get to such a system one would go into Bacon, go through Bacon's static, go to the wormhole designated 2, go through that system's static, and go through the hole designated 6).
Gets to be a mouthful on comms but it's worked for us so far. I am also a human, straggling between the present world... and our future. I am a regulator, a coordinator, one who is meant to guide the way.
Destination Unreachable: the worst Wspace blog ever |
The Cue
Applied Agoraphobia
9
|
Posted - 2014.03.10 17:06:00 -
[44] - Quote
Someone get Team Pizza in here to explain theirs, it's pretty convoluted. I've forgotten all the little nuisances, but it would eventually end up looking something like this: 121-11111
Anyway, most everyone uses a similar system to what we do, the first WH you find of any class is just that, each one afterwards gets a letter. Our static never has a letter, so even if you scan home and find another C4 first, it's C4a, static is always C4. ! denotes the way home. Carrots point which way the WH generated. BM starts with where you are, then where it goes.
So if our home system has an inbound C2 and C5, as well as our static, the bookmarks look like this: Mayhem < C5 Mayhem < C2 Mayhem > C4
Lets say our static has an inbound C4 and their static C4, as well as the WH in, the bookmarks look like this: !C4 < Mayhem C4 > C4a C4 < C4b |
Sandslinger
NorCorp Enterprise No Holes Barred
153
|
Posted - 2014.03.11 11:21:00 -
[45] - Quote
The Cue wrote:Someone get Team Pizza in here to explain theirs, it's pretty convoluted. I've forgotten all the little nuisances, but it would eventually end up looking something like this: 121-11111
Anyway, most everyone uses a similar system to what we do, the first WH you find of any class is just that, each one afterwards gets a letter. Our static never has a letter, so even if you scan home and find another C4 first, it's C4a, static is always C4. ! denotes the way home. Carrots point which way the WH generated. BM starts with where you are, then where it goes.
So if our home system has an inbound C2 and C5, as well as our static, the bookmarks look like this: Mayhem < C5 Mayhem < C2 Mayhem > C4
Lets say our static has an inbound C4 and their static C4, as well as the WH in, the bookmarks look like this: !C4 < Mayhem C4 > C4a C4 < C4b
Team pizza just copied Norcorps original bookmarking system that NOHO uses after they left NoHo. And no 121 could never go to 11111 neither could a 121 exist unless there was a dual wh static in 12 because 1 denotes static and higher numbers denotes K162. Sounds like Ragnarok has adopted our system too. stop spying on us
It's not that convoluted it was made before siggy and other usuch applics existed and using it means that when someone tells me their system I don't need to look at siggy to know how many jumps away they are and the route i need to take. |
hydraSlav
Synergy Evolved
44
|
Posted - 2014.03.11 12:57:00 -
[46] - Quote
The Cue wrote:so even if you scan home and find another C4 first, it's C4a, static is always C4.
How do you distinguish which C4 is static and which C4 is wandering, without first collapsing it and waiting for respawn? |
The Cue
Applied Agoraphobia
10
|
Posted - 2014.03.11 17:22:00 -
[47] - Quote
Sandslinger wrote:Team pizza just copied Norcorps original bookmarking system that NOHO uses, after they left NoHo. And no 121 could never go to 11111 It's not that convoluted once it's understood It could if there was a loop. :P Mostly I just haven't used it in months so I don't remember how it worked.
hydraSlav wrote:The Cue wrote:so even if you scan home and find another C4 first, it's C4a, static is always C4. How do you distinguish which C4 is static and which C4 is wandering, without first collapsing it and waiting for respawn?
You mean constellation statics? Since there's no way to tell, we just call one C4 and the other C4a. The important part is that an inbound can't be C4. This is one of those rules that came up from a confusing situation where someone had named them backwards. We missed a decent fight because of it. |
|
|
|
Pages: 1 [2] :: one page |
First page | Previous page | Next page | Last page |