Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 46 conversations about:
krazyken04
69
Aug 6, 2018
bookmark_border
Hamm3r
820
Hammer
Aug 7, 2018
bookmark_border
krazyken04Sorry Ken, the pics which MD took is oversaturation, they were not supposed to be black and red, the right color I take is close to Miami color, I promise the second thing you receive is the same as the sample I provided to MD.
chaseyeh0721
10
Aug 7, 2018
bookmark_border
krazyken04I only got replacement for Black, Teal, and Pink. No idea why no replacement for Red but perhaps Red color meets the spec in 1st batch. However, this is still quite disappointing cause the color should match Laser instead Miami. Will request refund from MD for sure.
krazyken04
69
Aug 7, 2018
bookmark_border
Hamm3rThis drop is for MiTo Laser, not Miami... the colors should be matching laser...
Hamm3r
820
Hammer
Aug 8, 2018
bookmark_border
speiszI really pointed out this mistake while the GB is active sir.
Hamm3r
820
Hammer
Aug 8, 2018
bookmark_border
krazyken04I know, but for some reason we still haven't received a laser color card from GMK, and Mito can't provide us with pantone colors. After negotiation, we decided to use Miami color which is really close to Laser's.
At that time, laser was just a render, and cyan and pink were not used as base color. This makes it difficult for us to accurately judge the color
Related Products
Drop Refurbished
Like-new products you can trustDrop Rewards
Get $5 for every 500 points you earn! Learn more
Drop Keyboard Club
Become a member and expand your keycap collectionFollow Drop
Both of these orders are for Red and Black... these are so obviously not what we bought... again.
That's not black, it's navy blue. That's not red... it's pink.
@Hamm3r did you even open these to see how off these are?
As a first time Hammer customer but a long time fan, this is really really disheartening.
I had looked at Hammer like it was top quality, but this will never match the Laser keyset, and it's occurred twice now with zero communication and months between updates.