These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Wormholes

 
  • Topic is locked indefinitely.
Previous page123Next page
 

WH BM naming convention

First post
Author
Tul Breetai
Impromptu Asset Requisition
#21 - 2014-03-06 06:53:24 UTC  |  Edited by: Tul Breetai
Jack Miton wrote:
People over complicate WH BM naming to all sorts of stupid ends.
BMs need to be unique only within a single system, NOT chain wide.

Oh, youre scanning a system and there are 3 C5s, a C3 and a NS?
Your BMs only need to look like this:

C5 In
C5
C5a
C3
NS

The BM tagged 'In' always denotes the route back towards home.
Here one of the C5s needs a lable since there are 2 unmarked ones.
The C3 and NS do not need lables since there is only 1 of each.

If youre too lazy to remember which hole you jumped into you can add the last 3 numbers of the target J sig to the BM name:

C5 (123)
C5a (456)

You never need the from system in the BM, it's the system youre in, really NOT very hard to figure out.
You also never need the sig ID in the BM, you just don't.

Couldn't have said it better myself. I've seen some pretty idiotic systems, naming conventions should be only as complicated as necessary.
Gnaw LF wrote:




Sorry but no, when I ping on comms or in intel channel that we have a fight in c5d, I dont want to explain how to get there. I also don't want to explain where to wait or where to form. Thus its helpful to have source > dest system because I only need to say "form up on c5d in c5c" when they select c5c -> c5d bm they know that they have arrived at the destination. You can also have multiple nullsec into the same region, you really want to have Source > Dest if you need to share or manage that BM.

You also don't need to describe the route via bms, all they need to know is which hole they're in, which hole they're headed, and which bm is to the next hole. Use a chainmapper.

There's nothing worse than an EVE player, generally considered to be top of the food chain in the MMO world, that cannot smacktalk with wit and coherency.

Gnaw LF
Viziam
Amarr Empire
#22 - 2014-03-06 07:59:12 UTC
Tul Breetai wrote:

You also don't need to describe the route via bms, all they need to know is which hole they're in, which hole they're headed, and which bm is to the next hole. Use a chainmapper.



I guess each and every group seeks the best system for their own needs, we use a mapping tool and still retain this convention. The convention was actually developed and used before the corporate bookmarks were introduced to EvE, Aquila retains the system because of a multitude of nuetral and awoxing toons we utilize for our purposes. It is fine if other groups don't want to use the same concept, but for us this system provides great benefit.
Mathieu X
The Scope
Gallente Federation
#23 - 2014-03-06 09:38:24 UTC
Hi,

We are a pretty new group and just moved in WH Space some days ago.
We use Tripwire and our naming convention is C2a for the first C2 accessible, C2b for the second, etc… For BM, we use folders named after System (ex. C2a, C2b, etc…) and put every BM into the specific folder. When we can not access a system anymore, we just remove a folder, this is pretty easy. We name the Wormhole with a “ > “ before (ex. > Home, > C2b, etc…). When we do not know the kind of system the WH goes into, we just put the 3 letters of the signature (ex. > ABC). We can recognize our statics (we live in C2 with HS/C3) without warping on them, but are still not good at recognizing others (if you have tips, I welcome them). This is how we do it, and we like it. Tripwire is amazing, thank to its Maker.

However, I always struggle to know the name of the signature I come from. When I find a new WH Space, is it an easy way to know the Signature Name? While writing it, I m saying to myself, maybe, if I launch probes on the entrance I will know immediately… Is it what you do?
ISD Ezwal
ISD Community Communications Liaisons
ISD Alliance
#24 - 2014-03-06 10:29:18 UTC
I have removed a rule breaking post and the one quoting it.

The rules:
4. Personal attacks are prohibited.

Commonly known as flaming, personal attacks are posts that are designed to personally berate or insult another forum user. Posts of this nature are not beneficial to the community spirit that CCP promote and as such they will not be tolerated.

ISD Ezwal Community Communication Liaisons (CCLs)

Bloemkoolsaus
Deep Core Mining Inc.
Caldari State
#25 - 2014-03-06 10:48:52 UTC
Gnaw LF wrote:

...................................................................................c2a
.....................................................................................^
...........c3z..................................................................c5c
.............^......................................................................^
c5y <- c5z <- Banana ->Static -> c5a -> c3a -> c3b - > lowsec
..v........................................................v
.c2z...................................................c5b -> nullsec


I have used several `systems` in my years, and can confirm that this one the most efficient. Every system in the chain has a unique name, so there is no confusing where you are, and where stuff is going down.

Bookmark syntax for us is always [current system] > [destination]. I like to put a star on the back bookmarks, so they show up first (back always refers to the home system). So if you're in c5a for exemple:
*c5a > static
c5a > c3a
c5a > c5b

This way, you do not have to look at j-sigs or at your mapper to see where you are, you know instantly by the bookmarks where you are, and where you need to go. Especially in large chains, this is really helpfull.
kparko
University of Caille
Gallente Federation
#26 - 2014-03-06 11:12:44 UTC
Mcpate came up with a new BM convention with our move from Low Class wormholes. Now that we are in big boy space all bookmarks look like this:

Here --> There
Meytal
Doomheim
#27 - 2014-03-06 13:17:51 UTC
When you have a dozen chains, each with multiples of every W-space system class, you find yourself needing to say things like "Targets in the C5c off Jita, form up at the C3d in C4a".

Those who can't understand this also likely struggle with L4 missions or with Hisec mining, which is where we suggest they go.


The reverse-naming for K162 holes is rather interesting though.

hydraSlav
Synergy Evolved
#28 - 2014-03-06 21:52:20 UTC
Bloemkoolsaus wrote:

Bookmark syntax for us is always [current system] > [destination]. I like to put a star on the back bookmarks, so they show up first (back always refers to the home system). So if you're in c5a for exemple:
*c5a > static
c5a > c3a
c5a > c5b

This way, you do not have to look at j-sigs or at your mapper to see where you are, you know instantly by the bookmarks where you are, and where you need to go. Especially in large chains, this is really helpfull.


Good point about using the name of the current BM to identify the "friendly name" of the system you are in without looking at the mapper. 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...

I think i will start dropping a generic random BM into the system with its "friendly name" to avoid redundancy of writing it in every other bookmark in the system

Mathieu X wrote:
However, I always struggle to know the name of the signature I come from. When I find a new WH Space, is it an easy way to know the Signature Name? While writing it, I m saying to myself, maybe, if I launch probes on the entrance I will know immediately… Is it what you do?

I do that, yes. Also, when you open your system map, the WH you just came through is marked on the map as "unstable wormhole" (although it's not warpable), in case you didn't drop the probes and warped off.

Thanks all for the feedback.
How do you maintain old/expired bookmarks? Since i play alone, every new day i login i simply wipe out by WH BM folder (since most of them expired already). Are there better methods?
Nelly Uanos
Stimulus
Rote Kapelle
#29 - 2014-03-07 01:36:19 UTC
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
Dark Venture Corporation
Kitchen Sinkhole
#30 - 2014-03-07 01:52:39 UTC
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
Gladiators of Rage
Fraternity.
#31 - 2014-03-07 03:47:58 UTC
I just call them all "your mom" as I jump in and out of them at will...

Icarus Able
Refuse.Resist
#32 - 2014-03-07 04:34:59 UTC  |  Edited by: Icarus Able
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
8 Sins of Man
Stray Dogs.
#33 - 2014-03-07 05:00:03 UTC
!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..
Bloemkoolsaus
Deep Core Mining Inc.
Caldari State
#34 - 2014-03-07 08:18:54 UTC
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 P
Lloyd Roses
Artificial Memories
#35 - 2014-03-07 10:02:03 UTC
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.
Lilli Tane
Deu-La-Deu
#36 - 2014-03-07 14:51:08 UTC
There is way too few information on that systems, a good BM naming system need to:
• Be easy to read
• Have all the information needed
• 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:
• All 5000 systems in eve,
• All WH types,
• Chains of 99 wormholes,
• Max mass allowance,
• time it was created,
• Solar systems with 99 wormholes,
• Max mass per jump,
• Mass status,
• Time status,
And it can be read at glance, and it’s easy to understand.
Blodhgarm Dethahal
8 Sins of Man
Stray Dogs.
#37 - 2014-03-07 18:25:54 UTC
Lilli Tane wrote:
There is way too few information on that systems, a good BM naming system need to:
• Be easy to read
• Have all the information needed
• 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:
• All 5000 systems in eve,
• All WH types,
• Chains of 99 wormholes,
• Max mass allowance,
• time it was created,
• Solar systems with 99 wormholes,
• Max mass per jump,
• Mass status,
• Time status,
And it can be read at glance, and it’s easy to understand.


Brilliant.. I will be immediately using this format.. 10/10
Kirasten
Perkone
Caldari State
#38 - 2014-03-07 18:58:43 UTC
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
#39 - 2014-03-07 19:32:34 UTC
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
School of Applied Knowledge
Caldari State
#40 - 2014-03-07 20:06:26 UTC
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..
Previous page123Next page