If someone ever asks me about that on my issue tracker, I'll just ban them."OK, I have the file open, but how do I change the numbers?"
If someone ever asks me about that on my issue tracker, I'll just ban them."OK, I have the file open, but how do I change the numbers?"
What if they can't 'change the numbers' as whenever they edit it, the game replaces their config folder. Thus, they cannot 'change the numbers'If someone ever asks me about that on my issue tracker, I'll just ban them.
I'll ban them, and send the report to Forge...What if they can't 'change the numbers' as whenever they edit it, the game replaces their config folder. Thus, they cannot 'change the numbers'
Nice to see you're consistentI'll ban them, andd send the report to Forge...
Everyone should be treated the same.Nice to see you're consistent
I had someone on this forum ask me how to read a crashlog.If someone ever asks me about that on my issue tracker, I'll just ban them.
Your crash logs are literally the most detailed I've seen. If you can't read that, how are you able to write, or login?I had someone on this forum ask me how to read a crashlog.
Someone else called them "mean" and "condescending" earlier.Your crash logs are literally the most detailed I've seen. If you can't read that, how are you able to write, or login?
That wasn't me...Someone else called them "mean" and "condescending" earlier.
I like my own version of SecurityException...Someone else called them "mean" and "condescending" earlier.
Exception in thread "main" com.coolsquid.Testy.Utils.Security.WTF_ARE_YOU_DOING_EXCEPTION: don't even try to override my securityhandler >:(
I think this should be readable for *users*.Not sure you developer types are familiar with them, but there are people out there who like to just use computers, not program them, and to them a crashlog is daunting and not at all clear even if they are able to read.
I think they are called *users*. Try to think like one every now and then.
Reika.DragonAPI.Exception.IDConflictException: The mods were not installed correctly:
The following ID conflicts were detected:
ID 15256: item.item.placer is being overwritten by item.PamHarvestCraft:potItem
ID 15257: item.item.electriingots is being overwritten by item.PamHarvestCraft:skilletItem
ID 15258: item.machine.wire is being overwritten by item.PamHarvestCraft:saucepanItem
ID 15259: item.machine.battery is being overwritten by item.PamHarvestCraft:bakewareItem
ID 15260: item.item.crafting is being overwritten by item.PamHarvestCraft:cuttingboardItem
ID 15261: item.item.electricrystal is being overwritten by item.PamHarvestCraft:mortarandpestleItem
Check your IDs and change them if possible.
This is NOT a mod bug. Do not post it to the mod website.
^ It is true, they don't understand crash logs...unfortunately we have to design for the lowest common denominatorNot sure you developer types are familiar with them, but there are people out there who like to just use computers, not program them, and to them a crashlog is daunting and not at all clear even if they are able to read.
I think they are called *users*. Try to think like one every now and then.
That might be true, but if anyone ever reports this, I'm banning them from the issue tracker.^ It is true, they don't understand crash logs...unfortunately we have to design for the lowest common denominator
com.github.coolsquid.SquidUtils.Utils.Exception.InvalidConfigValueException: The config value "forceDifficulty" has an invalid value
THIS IS NOT A MOD ERROR. DO NOT REPORT THIS!
Yeah that is just kinda stupid...unless they actually didn't see it past all the fluff -_-. That is the problem. A user sees a crash log and there immediate response is to report it; they don't even read it because they are daunted by it allThat might be true, but if anyone ever reports this, I'm banning them from the issue tracker.
Code:com.github.coolsquid.SquidUtils.Utils.Exception.InvalidConfigValueException: The config value "forceDifficulty" has an invalid value THIS IS NOT A MOD ERROR. DO NOT REPORT THIS!
If they don't even put in the effort to read the crash, I would either ban them or ignore them. It's not worth having users that don't even look at crashes.Yeah that is just kinda stupid...unless they actually didn't see it past all the fluff -_-. That is the problem. A user sees a crash log and there immediate response is to report it; they don't even read it because they are daunted by it all
Exactly, don't punish users for being users. It's already very nice to get reports on the issue tracker, as opposed to an unorganized forum thread. I know it's a good feeling to have achieved something, and your own mod that has a substantial userbase is definitely something to be proud of, but boasting "I'm banning people for this" before it even happened is ... unnecessary.Yeah that is just kinda stupid...unless they actually didn't see it past all the fluff -_-. That is the problem. A user sees a crash log and there immediate response is to report it; they don't even read it because they are daunted by it all
It's totally ok to be an user, but users could at least LOOK at the crash report!Exactly, don't punish users for being users. It's already very nice to get reports on the issue tracker, as opposed to an unorganized forum thread. I know it's a good feeling to have achieved something, and your own mod that has a substantial userbase is definitely something to be proud of, but boasting "I'm banning people for this" before it even happened is ... unnecessary.
We are designing for users, and users don't look. There's nothing we can do about that besides educating people about it and making our logs easier to read. So we design for users that don't look at logsIt's totally ok to be an user, but users could at least LOOK at the crash report!