When using "Register as spot color /register as color" can existing spot colors be bypassed ?

[Boldline]

Is there a way VS could recognize that an existing color is already a spot color and bypass making another copy of that color in the palette menu? I love the feature that will turn any added color into a spot color, but if I use a color in the existing spot colors of the palette, it should not make a new one, it will just lead to confusion

You can see in my example I used a teal spot color to change the artboard color and it made a new spot color for it - then I had used a light blue in the design initially, using the light blue existing spot color and it ended up making another.
I sampled all the other colors in the design aside from the black from a photo reference I pulled in, but none of those became spot colors...

[VectorStyler]

@Boldline If the color has a name, it will search the palette for a color with that name, and if found and the color matches, then it will not register it.

Should it search for a color only?

[Boldline]

@VectorStyler So with a little more research I discovered the issues happens when I source a color from another palette; in this case, using the color bar I have vertically placed on the side of my UI. So even though both my main color palette panel and the vertical color palette bar are using the exact same palette ase file, if I click on a color from the vertical color bar, it treats it like a "new" color in the color palette panel.

Here is a vide of this - you can see at the end when I started choosing colors from the vertical color bar, they began adding themselves to the main color palette.

I was reading in the documentation about the color palette bar and the first paragraph says, "The main Color Palette, stored with the document (but also other palettes), can be displayed in a narrow view at the side of the document window (at the bottom by default). The color palette displayed in this form allows quick access to the main color palette of the document, while taking away as little space as possible from the screen available for the illustration."
I understood this to mean the color bar palette could be a faster way to grab a color than to open or keep open the color panel and thereby conserve screen real estate. In my case, I'm I've literally loaded the exact same ase file into the default document color palette as well as into the color bar palette I have vertically placed in the UI. So it's confusing why choosing a color from the vertical color bar results in the main default color palette panel treating it like a foreign new color.

In my workflow, I would ideally have my streamlined commonly used spot colors set as my main color panel default palette and use the same palette file to populate the vertical color bar. I would then open another color palette that held ALL the pantone colors in an existing set. this way I could easily access a spot color I use frequently from the vertical color bar and go find a specific color I need from the larger set if it's not a common use color in the more accessible vertical color bar. I hope that makes sense
I'm far less likely to use the vertical color bar if it's going to cause repeat colors. I guess I could turn that setting off, correct? I understand why it puts a copy in the main color palette panel - because those are the colors VS will look at when exporting or preparing for print. If I pull a color from the vertical color bar and have the "register as spot color" off, and then go to export the file or print, is it going to recognize that color (if both palettes are using the same default ase file)?

[Boldline]

@VectorStyler said in When using "Register as spot color /register as color" can existing spot colors be bypassed ?:

If the color has a name, it will search the palette for a color with that name, and if found and the color matches, then it will not register it.
Should it search for a color only?

If both the vertical color bar and the main color palette panel are using the exact same ase file, wouldn't both be using the same names for their respective colors? If I pick a blue 286C from the vertical color bar, why would that create a new 286 C blue swatch in the main color palette panel when there's already an identical blue 286C in there?

In the screenshot below my (invisible) cursor is hovering over the Blue 286C in the vertical color bar palette and I'm showing the same ase file loaded as the main color palette in the document that has the exact same name - yet if I click on the vertical color bar version of 286C, it will create a new version of in the main color palette panel

[VectorStyler]

@Boldline It looks like the side-docked palette is different from the main document palette.
In the side-docked palette menu, select Show Palette -> Palette to show the current document color palette.
In this case extra colors will not be registered.

[Boldline]

@VectorStyler I realized the post from earlier in this thread is lacking the video. Here is that video where I had the same palette open in two locations and at one point adding colors from the vertical color bar kept adding new spot colors to the main palette panel. Jump to the 55 second mark.
UPDATE: I did as you suggested and think I am understanding the issue. I set both the main color palette panel and the vertical color bar to the same palette and they acted like they were different palettes - hence the video link I shared above in this post.
But I had to call them both the "palette" so that each was linked. This gets confusing because now both palettes when hovering over them refer to themselves as "palette" which I understand represents whatever palette was saved in the document settings - but it's not showing the palette's actual name.
Why is it not good enough to just load the same palette into both locations? VS needs a special setting to link the two in order for it to treat them as the same?