So I went to the sources tab to do what you said and had it watch through, and I get the what I assume is on of the variables being "self". And hovering over or around it shows me different other functions of sorts, I'm not entirely sure what I should be looking for or if this "self" is the answer (Or if I'm doing this right). By malformed custom language do you mean a different set of dialects? (Like the Rivals of Aether dialect/api since I did get that at one point and added it in the api files, which isn't there now considering the redownloads) Or do you mean mistypings/grammatical errors or maybe that athis self thing is the one affecting the functions in some strange way.
You would want to click on the nearest snippet in the code, so “app.js:6015” (new gml_GmlVersion), or click on the function in Call Stack (if you have used GMS1/GMS2 debugger in past, this is about the same).
And yes to dialect; since they are extracted to AppData, it’s probably still there if you haven’t manually removed GMEdit directory after deleting the app’s folder.
I think this is right? Clicking the top snippet sent me to the code that I've highlighted here. within the if statement for dir.
var gml_GmlVersion = function(name,dir,isCustom) {
this.isReady = false;
this.name = name;
this.dir = dir;
this.isCustom = isCustom;
if(dir == "api/none") {
this.config = gml_GmlVersionConfigDefaults.get(true);
} else if(Electron_API != null) {
this.config = JSON.parse(Electron_FS.readFileSync(dir + "/config.json","utf8")); <--- Here
} else {
this.config = gml_GmlVersionConfigDefaults.get(name == "v2");
}
};
Also I did try checking for if there was anything wrong within AppData to try and remove, but I either couldn't find it or that it's within a more complicated file I'm not aware of. In which case which folder would I find the outdated/malformed dialect in AppData? The only thing I can probably think of is that the RoA api I mentioned earlier being somewhere in my steam folders or something might be adding to the issue but I'm not sure if that's really relevant or not, unless it automatically tracks for dialect's or api's from previous versions maybe.
Thank you very much!
I had actually stopped using it since it hadn't entirely kicked in at the time so it didn't show me the problem, until now when I tried reinstalling it once more. And now it had shown me the problem! :D
Turns out I apparantly had the smart idea at the time to test making my own dialect for it despite not knowing how to do so and without adding a whole lot other then reference code from the roa dialect from earlier, knowing this now makes me feel very stupid. Still at least this will help others with more serious error issues, which I respect very much.
Sorry also that I hadn't given thanks a lot earlier, keep up the great work all the same!
