Not sure if it was always like this but Panel Loops add an extra loop when 1 is selected. I noticed by chance. Fix it for 2022 too 
Hello @KorayAtes ,
Iâm sorry youâre encountering something unexpected here. This is unchanged from any previous version of ZBrush. Please hold Ctrl and hover over the âLoopsâ slider next to the Panel Loops button. Youâll note the description there reads âPolygon Loopsâ, not âEdge Loopsâ. This is the number of polygon loops that will be created in the bridge area between panels, and these radiate out from each affected polygroup. If two polygroups are affected by the operation, they will each add that number of polygon loops in the bridge area. This is in addition to however many loops the feature decides it needs to create the sides of the panel based on bevel and smoothing settings.
Panel Loops creates both a âpanelâ and a bridge area between the panels. The panels have a side that is separate from the bridge area, and the number of polyloops created here will depend on your bevel and smoothing settings. Further information can be found here.
To create the minimal amount of loops, use the partial visibility option so that loops are only generated for the target polygroup, and reduce Bevel and Smoothing to zero. The minimal number of loops this will ever produce is twoâone for the side of the panel, one for the bridge.
Panel Loops are not a precision modeling feature. It is designed to be a fast solution for more complicated models. Adding a single edge loop to simple geometry like this is an easy task that can be accomplished many ways in the program. In this case the âEdge Loopâ feature in the same menu may create more predictable results. Likewise, Zmodeler Edge > Insert> Edge Loop, Polygon > QMesh> Polygroup Island, Edge> Bevel> or Polygon> Inset are all possibilities.
Even if it were a bug, ZBrush 2022 is a legacy version of the program and will not be updated further.
Thank you 
1 Like
Problem is, if âdoubleâ is not turned on you wouldnt know the second one is there and flipped. I noticed after some other operations started acting weird 
Not a regularly used operation and there are a few other ways to do it correctly even in the LEGACY version