The following extensions of mine have been updated for compatibility with v2024 Ruby - the deprecated Fixnum has been removed.
https://sketchucation.com/pluginstore?pln=ExtrudeTools - v6.0
https://sketchucation.com/pluginstore?pln=Latticeizer - v1.9
https://sketchucation.com/pluginstore?pln=Roof - v6.0
https://sketchucation.com/pluginstore?pln=SKMtools - v20240425
https://sketchucation.com/pluginstore?pln=TIG_Smart_offset - v4.0

v5.0 of PurgeAll is available - it fixes some minor glitches with v2024 changes...
https://sketchucation.com/pluginstore?pln=PurgeAll

@i5963c
The reason the toolbar appears is, because there are updates available - hence the red marker on the first button - not present otherwise.
If you open the ExtensionStore dialog and choose to install the updates, then close the toolbar, when you restart SketchUp the toolbar stays off, until you next activate it.
If you don't want the updates simply dock the toolbar in the side bar with others, it's unobtrusive...

@sashapepperspray
The method File.exists? has long been deprecated, but worked.
In the latest Ruby version it doesn’t - File.exist? - works in v2024 and older versions as well.
Many developers are working to adjust their code accordingly.

Have patience and post any instances in an affected extension's thread - as there are 100s of 1000s of line of code with the tiniest corrections needing to be found and change, then the extension re-encrypted and signed…

Many authors have already fixed their extensions, so look regularly to see if there’s already an update available…

@Joel3dm
Yes.
Make the non-auto-updating SectionCutFace unLocked and choose a material/color that's already used in the model [from a list].
A SCF's material applies to all faces, but you can edit the group and apply any material to any face etc...

Use the Outliner.
You can then expanded the 'tree' and select the nested Container, and double-click it in the Outliner to edit it that way.

v5 is now available in the PluginStore / ExtensionStore³
https://sketchucation.com/pluginstore?pln=Multiple_Offsets
It's now compatible with the newer SketchUp version's Ruby methods [e.g. 'FixNum' was deprecated in favor of 'Integer']
The RBZ is now also 'signed' to suit all Loading Policies...

You can't do that in one step. Do this.
Use the Tape-measure tool to make the first at 1/2" as before click to confirm, Select the guide line, and chose the Move tool, press Ctrl to invoke Copying, make the copy off 1/2" and immediately type 9x press Enter to confirm.
Now you have 10 guides at 1/2" spacing.
You can make multiple offset copies of selected things, including guides, but you can use the Tape-measure tool to make more that one guide at a time.
You can also make radial copies at set angles using Rotate + Ctrl for Copy and entering the number needed, press enter.
It's probably best that when inputting lengths or angles to the use 9x rather than x9 as the leading letter might sometimes get confused with ab x shortcut.
To make guide copies at a set spacing, e.g. use 9x but if you want to divide between a start and end guide manually pick the start and the final one and use 9/ to divide - that way you don't need the exact dimension, but can be sure the spacings are all equal.

AI forgot the doors !
Otherwise it's pretty good...

@Rich-O-Brien

Liam, get as well as you can soon...

Reminded me of this dickwad

Thomas Midgley Jr. has been named a “one-man environmental disaster” for two big reasons. He was one of the early pioneers of chlorofluorocarbons (CFCs) – compounds that became widely used in industry – and which were destroying the ozone layer. He also invented leaded gasoline and insisted that it was safe to use.

Perhaps there is a god, because after that he got polio and was partially paralyzed, he invented a pulley contraction on his bed to move him, but one day he became entangled in it and was strangled !

I'm not AI.
BUT I'll outline the steps for you...

Run these snippets in the Ruby Console.

1. Find all 'containers' [i.e. groups and component-instances].

2. Decide if you want to process all of them in your model. OR those in a selection. Here are the two ways a and b.

3a. #code

model = Sketchup,active_model
containers = model.definitions.to_a #an array of ALL groups and component definitions, including any nested ones.

OR
3b. #code

model = Sketchup,active_model
selection = model.selection
containers = [] #an empty array
selection.each{|e|
  next if ! e.is_a?(Sketchup::Group) || ! e.is_a?(Sketchup::ComponentInstance)
  containers << e.definition
}
containers.uniq! #ignore duplicates
#containers is now an array of selected groups and component-instances' definitions, BUT not any that are nested.

4. #use puts to see the results, e.g.

puts containers

Process [scale ?] the array of the 'containers' as you desire... one at a time e.g.

containers.each{|e|
  # whatever...
}

If your AI is clever enough. you need to ask it how to process the entities inside definitions [i.e. components and groups] using an iteration...

Perhaps the best Fredo idea yet !

You seemingly haven't installed it from its RBZ.
If you simply copy the ../Plugins/HouseBuilder_extension.RB file over to the newer SketchUp version it misses the images to make the toolbar-buttons [and worse!]...
Unfortunately the original author was in the dim past [20years ago] and made a half-baked extension loader file, and he didn't give his subfolder the same name as the RB file.
The new[ish] auto-migration tool assumes this file/folder naming convention and so it misses out copying the subfolder of images [and some other vital support files that are in that folder].
To fix it you need to find the whole HouseBuilder folder [and its contents intact] in your older version's Plugins folder and copy that whole folder over into the newer SketchUp version's Plugins folder.
When you startup SketchUp it should now find the subfolder and load the buttons' images and the other vital support files...

Thanks for the update.
You saved me from doing the work !
Seems to work as it should with undo and so on.
Much better structured code-set.
The code # rem's are much more helpful.
It needs more guidance about the settings and what they do.
Also on how the 'red' mesh areas control the results.
Is the new mesh meant to be colored without any choice ?
It's neat, but perhaps not always wanted ?
You could add a simple checkbox option to the dialog - 'Color by Z height'
then skip that coloring part around line#279=#291 if it's set 'off'...

Before trying the following please read the whole post as the answer might be a misunderstanding...

1. Use the SketchUcation ExtensionStore to install JointPushPull, FredoCorner and LibFredo6 again.
   Then restart SketchUp to sync everything.

2. If you are still getting the licensing error[s] check that you have installed the proper license for the extensions

• I suspect that you have a license for Fredo's RoundCorner and this is not the same as the installed FredoCorner, which expects a separate license file.
  There have been a few reports of users confusing the two extensions and their respective licenses.
  Although the two are similar in what they do, they are not identical, and they need to be licensed separately.
  So ensure you have the correct extensions installed and their matching licenses validated,
  after that a SketchUp restart should get both properly licensed and error free.

Try visiting the owner's website and follow the instructions carefully.
The things you need to select to get the tool to work is a little complicated, but once you understand it it's pretty straightforward...

v5 is now available in the PluginStore / ExtensionStore³
https://sketchucation.com/pluginstore?pln=Multiple_Offsets
It's now compatible with the newer SketchUp version's Ruby methods [e.g. 'FixNum' was deprecated in favor of 'Integer']
The RBZ is now also 'signed' to suit all Loading Policies...

I was also looking ! It seems to be a simple issue with 'FixNum' being deprecated in the newer Ruby version, replaced by 'Integer'.
I'll edit the file and publish an updated version asap.
Under the author's notice it's allowed...

Any error messages in the Ruby Console ?
Are you following the detailed instructions.
It hasn't been supported for sometime - the author has stopped all development on his extensions.
Although it's old it has been reported as working in versions up to a few years ago...