#I have pro version, but still getting "Made with Needle" text in inspect element.

1 messages · Page 1 of 1 (latest)

peak lance
#

Hi, I have pro version, but still getting "Made with Needle" text in inspect element in html. Do i need to enable/disable any options?

image.png
elfin epochBOT
# peak lance Hi, I have pro version, but still getting "Made with Needle" text in inspect ele...

Thanks for reaching out @peak lance

Please read through the following and share the information requested. This will help us to better assist you.

Description

Describe the issue that you're seeing. Please be as detailed as possible e.g. is this issue happening in Unity or Blender, which Needle Engine version are you using, do you see any errors in the Editor or Browser console, etc.

Information:

  • If you're using Unity click the menu item Needle Engine/Report a Bug/Copy Project Info to Clipboard. Please share the results below.
  • Please provide code snippets using Discord Code Blocks
  • Have you contacted Needle through another channel or just through Discord?

Thanks for submitting!

💡 Did you know that we now also have a forum with AI support? Join now with your discord account!

cosmic cloud
#

Hey, would you mind clarifying why you think this is problematic?

peak lance
#

Hey,

Absolutely, happy to clarify! While it's true the "Made with Needle" text isn't visible directly on the frontend, it's still part of the site's HTML code, which can be viewed by anyone who inspects the page. This matters to us because:

  1. Professionalism and Branding: We aim for a fully branded experience, even in the details. For clients or partners who might inspect our site, it's important that every aspect reflects our brand, not a third-party tool.
  2. Competitive Edge: In our industry, the uniqueness and ownership of our digital presence are key. Even subtle third-party references can raise questions about our autonomy in creating and managing our tools.
  3. Pro Version Benefits: We upgraded to the Pro version specifically for features like custom branding, which we understood would cover all aspects of the tool, including the codebase.

We hope this clarifies our position. If there's a workaround or a setting we might have missed, we’d really appreciate your guidance!

Thanks for your understanding and help.