Thread: Breaking Extensions so much
-
November 14th, 2024, 15:52 #81
- Join Date
- Feb 2017
- Location
- Greece or Iceland, depending on the time of year.
- Posts
- 215
I dunno if I agree with your thesis. I'm no coder, but 9 times out of 10, I can figure out which extension is throwing the error from the error-message in the console. For instance, if I have an error that says something's wrong with the CT, and I have an extension that alters the CT, chances are, that is the extension that's causing it.
-
November 14th, 2024, 16:10 #82
Error messages include a reference to the base code that raises the error - this will include the ruleset or extension name. My only gripe with the message is that if the path to the ruleset/extension file is long it gets truncated - it would be nice if the whole path (ruleset/extension: path to file) was included in the message and not truncated.
Private Messages: My inbox is forever filling up with PMs. Please don't send me PMs unless they are actually private/personal messages. General FG questions should be asked in the forums - don't be afraid, the FG community don't bite and you're giving everyone the chance to respond and learn!
-
November 14th, 2024, 17:45 #83
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 21,430
Yeah, I would love that too. Unfortunately, for whatever reason, the Lua script engine limits code block identifiers to 40 characters.
Regards,
JPG
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks