The Renderfarm

1:14 AM

@JachymMichal not trying to be picky or mean but you dont need to start your custom CV reasons with "Respectfully." I expect the op will either understand about the question getting closed, or will get mad. I highly doubt adding "Respectfully" will make it any better.

PS mods @DuarteFarrajotaRamos (you are the only one pingable) you should consider adding a custom CV reason that says something along the lines of "This question is not about Blender." I see lots of custom messages written with that theme.

also @DuarteFarrajotaRamos I dont think [blender.stackexchange.com/questions/215367/… is deleted, just locked. certainly could be deleted.

Jachym Michal

5:55 AM

@David Noted :)

Rithaniel

6:28 AM

Hello, I've recently tried writing a blender add-on, but I'm encountering an issue. I'm stopping by, here, first, as I'm unsure if it's sufficient for its own question on the stackexchange. I'm getting an error that starts with

location: <unknown location>:-1

Also, I can't seem to get the command to appear in the operator search, but I think it's related to this error. The traceback gives this

File "C:\Program Files\Blender Foundation\Blender 2.91\2.91\scripts\addons\ant_landscape\ant_functions.py", line 187, in poll

Duarte Farrajota Ramos

11:59 AM

@David I would have sworn the system removed migrated questions automatically

Thanks, removed now

Duarte Farrajota Ramos

12:19 PM

@David That has come up a few times in meta, some of them even posted by you

8

Q: New off topic close reason

There is a consensus that we have to do something to address posts that are off topic. See all the previous meta posts: Add a “Closing > Off-Topic > Not about Blender” reason How should I flag tutorial requests? Cleaning up our custom close reasons Custom off-topic close reasons: 2014 in review (...

8

Q: What should our custom off-topic close reasons be?

Custom close reasons have been live for a while now. We currently have 2 of the (3) given in use but a recent surge in questions being closed has prompted the need for a few more that are more tailored to address specific questions/close reasons instead of writing up why it is off-topic everytime...

discussion questions scope close-reasons

8

Q: New off topic close reason

There is a consensus that we have to do something to address posts that are off topic. See all the previous meta posts: Add a “Closing > Off-Topic > Not about Blender” reason How should I flag tutorial requests? Cleaning up our custom close reasons Custom off-topic close reasons: 2014 in review (...

discussion close-reasons

8

Q: Custom off-topic close reasons: 2014 in review

The last new off-topic reason here was added on January 14, 2014 - one year ago today. So now is a good time to review how these have been used over the past year, and consider if changes are necessary. I pulled together some basic information to further this discussion: Off-topic reasons Activ...

discussion close-reasons

We only get three, as far as I know. Is "not about Blender" really the most used custom one, or does it just get picked automatically as generic reason when there is no consensus on a single close reason?

@Rithaniel that error message alone is insufficient to diagnose the issue.

Why don't you post a full question with the relevant code excerpt that i causing the issue so we can diagnose it?

David

5:13 PM

@DuarteFarrajotaRamos nope that list I linked are all messages users typed out to close questions.

True that without asking sites only get 3 custom reasons, yet BSE is only using two of our three (and have only been using 2 since we redid the CV reasons in 2015).

Seems that if there is a continually used theme, why not make it a custom reason. and save users a bit of time.

yah I have brought that up a few times in the past... another example of something that went to meta to die.

Duarte Farrajota Ramos

7:52 PM

@David It seems it is not easy to modify close reasons after they are creates, so not to leave closed questions with that reason "orphaned" or closed with a now completely different reason that no longer matches the original one

11

Q: How do I edit custom close reasons?

There's a typo in one of our custom Off Topic reasons and I need to edit it, but I don't see an edit button: How do I edit an already active close reason? Do I have to deactivate the existing one then add a new, corrected custom reason, or can I edit it after deactivating it and reactivate it ...

support moderator-tools custom-close-reasons

so it should be done carefully, ill contact the other mods, maybe make yet another meta post

but this time I'll see it through ;)

David

8:52 PM

@DuarteFarrajotaRamos its not hard to change the custom reasons, but yes they can not be edited after live. (takes multiple mods to vote to activate it.) However no reason you could not deactivate it then create a new one, if for example someone misspelled "dowload."

we did that back when we changed the wording of the bug report message.

If I remember correctly this should be the page to edit the custom CV reasons. its just a 404 for me now:(

Duarte Farrajota Ramos

@David that is correct

I was also digging through meta posts to find how to reach that page

I'll make a meta post about it when I get the chance, and ping you about it

David

sorry you had to search for it.

it is linked from the admin dashboard, under the links heading (I think)

Duarte Farrajota Ramos

@David Yeah, no problem actually made bother to look through those with more attention, now I know how to get there

David

@Rithaniel you will need to post more information then that in your question. The full console output with the error. Also your addon name, because the partial error you posted here is from the ant landscape addon.

Transcript for