Rename module to custom multi value field

Sorry but I strongly disagree with the statement that the name is confusing and doesn't explain the purpose of the module. "Custom field" explains exactly what the module provides... a field that is "custom" meaning that no assumptions are made how the user wants to compose a field and using the field types and widgets this module provides allows the user to make indeed a "Custom" field to their desire. I'd say if this module was ever to be made a candidate for Drupal Core, let the powers to be debate a more suitable name but we are a long ways from that consideration. I do appreciate you using the module however and the consideration of its future. Please continue to promote the merit of its usefulness to the community and ultimately a larger community base speaks louder than you or me alone in the viability of it being a staple module. Thank you!

What if someone who is new to drupal googles: how to create a custom field in Drupal?
Have you considered that duplicity in meaning?

What if someone googled "how to create an address field in Drupal" and landed on the Address module page? Personally, I really don't see the issue. Honestly, why would someone want to create a "custom" field manually when my module provides all the scaffolding to handle majority of use cases? So YES, I want people to search "custom field" and land on my module page which saves them a significant amount of time in what would normally require a considerable amount of time to scaffold all the files to together. The ability to do this through the UI in my opinion is a huge advantage over other CMS's and encourages a field architecture that is frankly a whole lot better than the archaic every field is a table concept. To answer your question, yes I have considered the duplicity in meaning and it is very intentional by design. I think it's good as is but people can certainly choose to just not use it if they object to the name or anything else. Open source is a wonderful thing ;)