I'm having an issue opening a patch since it crashes every time I try to open it. It started crashing when I tried to encapsulate a big part of the patch and closed abruptly and I can't open it ever since, so the issue seems to be in the encapsulation or a loadbang issue. Is there a way to open it in safe mode or at a previous save point?

@DimitriosG I think the only way to recover the patch will be to open it in a simple text editor and try to see what is wrong.
If you compare it to a working patch then you should be able to fix it.
Look especially at the lines that start with #N or #X restore as they define the canvas for the patch and any subpatches .......

#N canvas 96 177 450 300 10;
#N canvas 255 338 450 300 subpatch 0;
#X restore 106 87 pd subpatch;
#X obj 108 21 loadbang;
#X msg 108 57 \; pd dsp 1;
#X connect 1 0 2 0;

Renaming any [loadbang] objects to [loadbang-off] might well help as a first step.
The objects will be listed in the order in which you created them..... so you should check the last objects in the list, just before the first #X connect.

You can find information about the lines of text and their meanings here..... https://puredata.info/docs/developer/PdFileFormat
With luck it will be the same formats for PlugData as for Pure Data, as I think the patches are transportable.
If you don't succeed then upload the file to the thread and someone might have more luck.
David.

@DimitriosG I would expect the standalone version of PlugData to have something like vanilla pd's -noloadbang startup flag, I'd even expect it too use the same flag as pd just for sanity's sake but who knows. But renaming any [loadbang]s from a text editor generally does the trick,

@whale-av said:

Deleting any [loadbang] objects might well help as a first step

You mean renaming, deleting will generally have disastrous results since it will throw off object counts in the connect messages.

@oid Well spotted. I have edited my post in case the op reads no further.
David.