I don't think it does. The Widgetize basically converts all objects(units, heroes, items) into a different format which can be accessed alot easier, thus speeding up loading time.
No, I meant how come certain maps, after playing them and you change the map to something like dota, everyone will dc in the first 10 seconds.
Example. I amd playing map A. After I am done, I play Map B, in the first 10 secs, everyone in the map dcs. To solve this problem, wc3 needs to be restarted. Does the widgetizer do this?
I've never experienced this myself.
So I wouldn't know.
There are also a lot of reason behind custom maps crashing. But I don't know. Is it the same problem with the same map everytime?
This is a bug (or atleast a weird thing) in wc3. I don't know the exact reason but it has to with with how wc3 loads object data from a map and doesn't unload it until you close wc3.
I think that wc3 has 2 different files for it's unit data, one is used for those units that are in wc3 by default (ie footman) and this data isn't unloaded until you close wc3.
Then there is a second file type for the custom data in a warcraft map, this data is unloaded as soon as the map ends.
The first file type is faster than the second and the widgetizer has an option that converts the 'slow' files to 'fast' files, this has the side effect that wc3 never unloads the data when the map ends and that can create conflicts with other maps.
But, as I said, I don't really know if this is true. Someone that is more educated on the subject may clear things up.
From what I heard this bug only existed with Doodad/Desctuctable optimization and its supposedly fixed now.
It used to cause the next map you load crash...namely this happened to ToB.
Either way you should be safe if you turn those two off. Not sure though, this might as well be a completely different issue you're talking about.
Anyway this is how I understand what widgetizer does:
Custom object data is stored inside a special, separate file in every map. This data has to be converted intro the native SLK format while the map is loading in order for Warcraft to use it.
Now widgetizer simply does this once and saves the SLK data so that Warcraft wouldn't have to do it again while loading.
Yet as phyrex1an said its possible that the modified SLK data is kept when you load the next map which would obviously cause a crash.
Although I don't know if I need to actually actively heat it or just let the plate and hotend bring the ambient temp to whatever it will, but even then I need to figure out an exfiltration for hot air. I think I kind of know what to do but it's still fucking confusing
I don't think I'm dealing with quite the same pressures though, at the very least its a significantly smaller system. For the time being I'm just going to put together a quick scrubby box though and hope it works good enough to not make my house toxic
I do know this - xenforo dropped the ball by not keeping the vbulletin reputation comments as a feature. The loss of the Reputation comments data when we switched to Xenforo really was the death knell for the site when it came to all the users that left. I know I missed it so much and I got way less interested in the site when that feature was gone and I run the site.