You can!
Simply do:
icon:modifyTheme({
{"IconImage", "ImageRectSize", Vector2.new(A, B)},
{"IconImage", "ImageRectOffset", Vector2.new(C, D)},
})
I’ve also made this exact example in the v3 playground you’re welcome to check out:
and thanks for the reminder as I missed this initially 
Oh, that’s awesome! Thank you so much for your help! 
A design overhaul to match the new topbar…Icons, captions, dropdowns, menus… everything! v3 aims to mirror the topbar so you can seamlessly build upon it.
…but with inbuilt support for the old topbarNot all clients see the new topbar… yet. v3 solves this by listening for differences and adapting to a classic design accordingly.
A complete codebase rewrite and re-organizationReadability and performance have been the driving reasons behind this. By outsourcing logic to UIComponents and reorganizing instances into more appropriate containers the Icon and IconController have collectively shrunk from >3000 lines of code to ~1000.
An easier system to modify icon appearance and behaviorYou’re no longer limited to predefined settings… you can modify… anything! 
The way you modify icons has also changed to be more straightforward. More info on that here.
TopbarPlus is now a packageNo more faff when updating… just right-click the package, update and bam, all set! 
More details here.
TopbarPlus now supports WallyYou can find that here!
Improved support for gamepads and mobile devicesPretty much the title, lots of small improvements to make navigating icons on different devices that much easier.
Overflow upgradeOverflows now become horizontal menus instead of vertical dropdowns. More about that here.
Brand new documentationHappy reading! You can find the v3 documentation here.
MIT → Mozilla Public License v2.0You can use TopbarPlus free of charge. All you need to do is provide credit back to this resource (such as link to its devforum post) and to open source any significant changes you make to the package.
Backwards compatibility with the majority of methods from v2The majority of v2 methods and features have been built into v3 to make for an easy transition.
You can find a full breakdown of changes here:
You can transition over to v3 in a few easy steps found here:
v3 has a new playground where you can experiment with these changes and find pre-made examples:
@hayper1919 for multiple improvements to the repository, help introducing wally, code cleanup, and ongoing help with luau typechecks and luau autocompletes
@gitzerai for help with the transition to the new topbar
@iamEvanRBLX for the initial hybrid support for the new topbar
@LordMerc for help with the documentation and general feedback
@ValiantWind for help with testing and feedback
@2jammers for help retrieving values in features such as captions
@medallyon for help setting up Wally
@PeZsmistic for help with clamping objects within screen bounds
@pobammer for the package Janitor
@stravant for the package GoodSignal
Thank you to the many contributors of v3.0.0 and everyone who has provided feedback and reports over the last three months 
v3 alone has taken many months of work. If you’d like to support the development of TopbarPlus and similar applications it’d be great if you could check out the following:
I’ll continue to monitor this thread so feel free to share any feedback or issues you have.
Enjoy! 
Looks like the Wally package isn’t installing correctly. Might be an issue with the default.project.json?
Is there any way to check the dropdownIcons in v3 after the property’s removal?
We Got V3! I’ve been waiting for this since 16.10.2022! I used This Module Since 2.7.2 Version! Keep Up With The Good Work!
The topbarplus v3 came out before the one piece… That’s absolutely wild
Is there a playground for testing?
I’m looking into this, should hopefully have this resolved tomorrow.
icon.dropdownIcons still exists so you’re fine to use it. this is something I’ll likely add back into the documentation shortly (I just removed temporarily to get everything up to speed)
TopbarPlus v3 before GTA VI 
Good job!!
Also using v3. I also just noticed that the rounded corners aren’t as rounded as they are in CoreGui.
I’m still trying to decide if I should fix it myself or just deal with it until it’s fixed officially. It’s a minor issue that most players won’t notice.
Amazing! But by the way is there a way to enable/disable new chrome topbar?
Something like this could be fixed by adding a Y offset to themes I’d imagine
How do you make each menu/dropdown item do something different?
Okay, so I love v3.0.0, it’s great and everything but there is one underlying issue I seem to have found, which is when I use the :LoadCharacter() function it or if the character resets creates duplicates of each topbar element.
Context:
I have my local script in the starterGui that creates the topbar elements, and there is no errors
Screenshot:
I have solved the issue, and for those wondering the topbar script should not be in the startergui but in replicated storage and have a run context of client
you can do making a screengui and turn off resetonspawn then put your topbar script into screengui
or put your top bar script into startercharacterscripts.
yeah, I did solve my issue but I mean this might help others
I wanted to ask, what is the best way to credit this module or what ways are acceptable a few ways I’ve thought about:
Topbarplus V3 already prints out the console. So you dont need to do anything
