https://patchstorage.com/no-click-phasor-looping-w-tabread-pd-vanilla/

so if youre using an array of static the phasor and tabread are probably doubling the last numbers of the array. because the read head probably falls over the end mark.

But resize and [switch~] could both be causing clicks..... [switch~] definitely if it is being triggered.
"resize", in your patch, is not causing clicks as you are sending the message to noise-$0 and the array is named $0-noise.

So [switch~]
You are probably trying to soft fade as notes change and avoid clicks that way, but [switch~] is abrupt.
It would be better to soft fade using [line~] controlling the [*~ ] as below to fade out and in on each side of the switch.
David.

Here I have maybe softened the [switch~] .... that might help.......

EDIT... Error in previous upload........... per.zip
David.

When you are asking questions in the forum, please make it as easy as possible for us to answer and make some effort yourself!
Did you already search? Did you read the helpfile of tabosc4~ ? Did you read the helpfile of array-guard ? (here is the original post: https://forum.pdpatchrepo.info/topic/14301/add-delete-guard-points-of-an-array-for-4-point-interpolation-of-tabread4-ect )

What is it that you do not understand?
This forum is very helpful, but "I don't understand" is not not enough to give any answer.
If you want low-level, I recommend learn the basics by going through Vanilla's example patches and manual.

Don't want to sound like a gatekeeper or so but this is basic netiquette.

On your question about clicking:
a) What is a click? We hear a click when there is an abrupt change in the waveform.
b ) When does it happen? At the wrap around of the reading [phasor~]>[tabread4~]
c) There is a jump between the last sample and the first sample, so it clicks
d) How to solve this?
e) One way is to use a triangle-wave reading the array instead of a saw-tooth ramp. This gives us a continous loop back and forth without glitch.

I think @willblackhurst solution is similar, but instead of reading back and forth it builds an array by mirroring the original array, to build a continous loop.

As last step you can make the triangle drive the tabread4~ between guardpoints, but I don't think missing guardpoints are the reason for clicks.

(I am also missing externals to test the patch)

array-clicks.pd

Also you can drive Perlin noise directly without glitches, without an additional array.

I will try to explain my question in more detail:
I started with tabread4~ to be an oscillator with a sampled waveform of the perlin noise generator. Now I want to try to use tabosc4~ as I have an idea that it will work better... What I imagined is that tabosc4~ reads the table of the sampled bit of Perlin noise and I thought the guard points was there to make a fast crossfade between the end and the start of the loop... is this right? Anyways I tried to read how to add the start points and (that is how my brain works) didn't understand how to implement it. I thought you could add some extra samples to the length of the table and it would happen automatically but maybe im wrong... That is about as good as I can explain. Anyways I don't wanna bother anyone more with this, so if nobody is able to help or understand my question, ill just work around a homemade solution, that doesn't rely on stuff I don't understand

dumb questions

I didn't say that.

I thought the guard points was there to make a fast crossfade between the end and the start of the loop... is this right?

The "4" in [tabread4~] [tabosc4~] ect. stands for four-point interpolation. It inter-sample interpolates. This is useful when you read an array at different sampling-rate than the patch/system's sampling-rate. This happens if you change the read-speed or of the array or if it has different samplerate. By interpolating between samples you get a value anytime, even between samples.
The interpolation algorithm requires 4 points, and to work as intended, it requires an array-size in the power of 2 plus 3 samples have to be added at the edges of the array.
You can read about this in more detail in the array-guard helpfile and further links mentioned there.
There is also [tabread~] that does not inter-sample interpolate.

I thought you could add some extra samples to the length of the table and it would happen automatically

Take an array in the size of power of two (256 for example) and use array-guard to add the guardpoints.

But I don't think that the click is about inter-sample-interpolation-artifacts.
Check out the patch I uploaded in my last post.

crossfade between the end and the start of the loop

Yes, this would be another common way to get rid of the click.

Also, you can read Perlin directly, without array, check Perlin helpfile.

switching between each other and creating a crossfade

Pd Vanilla's example patches (I don't know if PlugData has them):
Read B.07.sampler.pd until B.13.sampler.overlap.pd