2 hours ago, ebmsebm said:

still crashing

My only other options are:

 

1.  Try disabling all plugins except LSPDFR

2.  Reinstall LSPDFR

8 hours ago, Rich said:

My only other options are:

 

1.  Try disabling all plugins except LSPDFR

2.  Reinstall LSPDFR

well i did both, so i guess i have to start over. thanks for your help

 

4 hours ago, ebmsebm said:

well i did both, so i guess i have to start over. thanks for your help

 

Make sure to choose your plugins and callouts carefully. Don't download out of date files 🙂

1 minute ago, Jeffdadawg said:

Make sure to choose your plugins and callouts carefully. Don't download out of date files 🙂

If only everyone did this...

3 hours ago, Jeffdadawg said:

Make sure to choose your plugins and callouts carefully. Don't download out of date files 🙂

what qualifies to you as outdated files? like updated over a year ago? or just a couple months?

 

I usually advise not to use anything older than 0.4.6 

2 minutes ago, Charlie686 said:

I usually advise not to use anything older than 0.4.6 

What is this based on?

Personal experience. I find any older LSPDFR API's cause more frequent crashes. Also following the advice I have seen given by @UnknownBastion

Obviously any old LSPDFR plugins come with a risk of crashes 🙂

4 hours ago, Charlie686 said:

Personal experience. I find any older LSPDFR API's cause more frequent crashes. Also following the advice I have seen given by @UnknownBastion

Obviously any old LSPDFR plugins come with a risk of crashes 🙂

The risk only comes from a new version changing an old API function.  If the plugin worked before an update, and the update doesn't modify any API features used by the plugin, then there's (in theory) no reason a new crash should occur.

8 hours ago, ebmsebm said:

what qualifies to you as outdated files? like updated over a year ago? or just a couple months?

 

Outdated files can be files that aren't optimized for 0.4.8

I would say that the time limit is September. Nothing before that unless it is a stable plugin with nothing related to what version it is. (Like Cop Holster, for example)

4 minutes ago, Jeffdadawg said:

Outdated files can be files that aren't optimized for 0.4.8

I would say that the time limit is September. Nothing before that unless it is a stable plugin with nothing related to what version it is. (Like Cop Holster, for example)

What do you mean by "optimized for 0.4.8"?

12 minutes ago, Rich said:

What do you mean by "optimized for 0.4.8"?

Updated for 0.4.8

SuperCallouts, for example. It was updated for 0.4.8

9 minutes ago, Jeffdadawg said:

Updated for 0.4.8

SuperCallouts, for example. It was updated for 0.4.8

This is only necessary if the plugin needs to use the new API features.  If a plugin doesn't need the new API features, then there's no need to update it just because LSPDFR was updated.  There is no "optimization" that automagically happens.

1 minute ago, Rich said:

This is only necessary if the plugin needs to use the new API features.  If a plugin doesn't need the new API features, then there's no need to update it just because LSPDFR was updated.  There is no "optimization" that automagically happens.

Well, the main point I was trying to get through was 'don't download outdated files'

 

Just now, Jeffdadawg said:

Well, the main point I was trying to get through was 'don't download outdated files'

 

I understand that; however, there should be an asterisk that mentions not all outdated files are inherently broken.  When I see people recommend removing all of Albo's plugins on the sole basis of them being old, it bothers me some.  Some of Albo's stuff still works just fine.

 

I would personally read the newest comments on a file to get a better idea of if it actually works or not.  Unfortunately, the caveat to that is people who break their games through no fault of the plugin in question can easily (and incorrectly) blame that plugin.

On 10/22/2020 at 12:49 PM, ebmsebm said:

 

RagePluginHook.log 151.63 kB · 11 downloads

I think I figured out what your issue is cause I just had the same issue now. I am using Ultimate Backup and my default regions xml file, lists the same zone multiple times within one region. This was the case for multiple regions where one zone was redundantly specified right after each other. Check if this is the case with yours.

 

I inferred it was ultimate backup since the very last message right before your and my crash is: UB: DEFAULT REGIONS FILE IS SUCCESSFULLY LOADED

6 hours ago, XTREMEHEAT said:

I think I figured out what your issue is cause I just had the same issue now. I am using Ultimate Backup and my default regions xml file, lists the same zone multiple times within one region. This was the case for multiple regions where one zone was redundantly specified right after each other. Check if this is the case with yours.

 

I inferred it was ultimate backup since the very last message right before your and my crash is: UB: DEFAULT REGIONS FILE IS SUCCESSFULLY LOADED

man i posted that 5 months ago, i've rebuilt my game 4 times since then. i will keep that in mind for the future though.