[Burichan] [Futaba] [Nice] [Pony]  -  [WT]  [Home] [Manage]
[Catalog View] :: [Archive] :: [Graveyard] :: [Rules] :: [Quests] :: [Wiki]

[Return] [Entire Thread] [Last 50 posts] [Last 100 posts]
Posting mode: Reply
Name (optional)
Email (optional, will be displayed)
Subject    (optional, usually best left blank)
Message
File []
Embed (advanced)   Help
Password  (for deleting posts, automatically generated)
  • How to format text
  • Supported file types are: GIF, JPG, MP3, MP4, PNG, SWF, WEBM, ZIP
  • Maximum file size allowed is 25600 KB.
  • Images greater than 250x250 pixels will be thumbnailed.

File 135568821143.gif - (0.98MB , 450x253 , tumblr_m9fk67qbuJ1r2h860o1_500.gif )
65302 No. 65302 ID: d6ae01

A script was recently written to make graveyard-ing semi-automatic. A mod can now just press a link and the server will graveyard quests that haven't been posted in for a couple months. This means three things:

1: It's nothing personal. If your quest is in the graveyard, it just means you haven't updated it in a while!

2: Don't report a quest to be revived unless you have an update ready to go. It will otherwise be thrown right back into the graveyard the next time the script is run.

3: Be doubly sure you report completed threads! A finished thread that isn't reported will get thrown into the graveyard by the cold unfeeling script.

I should also point out that due to kusaba limitations, you can only report a thread once, even after the report is cleared. Occasionally someone will go through and report every thread just to be a jerk, so I recommend reporting the second or third post in a quest waiting to be revived. Reporting the final update is fine for a quest being archived.

This thread will self destruct in a few days. Feel free to field questions here.
>>
No. 65303 ID: aff0c0

after how much time the thread get graveyarded, exactly?
>>
No. 65304 ID: d6ae01

>>479388
Looks like two months.
>>
No. 65305 ID: 4a20fa

>This thread will self destruct in a few days.
(Maybe move it to /questdis/, unpinned, then instead?)

What kind of interval are you going to be running this thing on?
>>
No. 65306 ID: d6ae01

>>479465
(Sure, that works)

That is mostly up to the graveyard mod, but I would wager every 1-2 weeks. Every mod has access to the button, so it might get pressed by them on occasion as well. If all that fails, I would likely press it myself after 3 weeks of non-pressing.

In general quests will get moved there more often, but I'm hoping the stigma or implied insult of it will be lessened by the fact that it's done by ~*magic*~

I'm saying Dylan's coding is magical.
>>
No. 65307 ID: 62496e

>>479475
>inb4 the script malfunctions and graveyards every single thread
>>
No. 65308 ID: 0f60d7

>>479486
No, I'm pretty sure that won't happen twice.
>>
No. 65310 ID: 4a20fa

>>479486
That's fine; just write a similar script to move recently-updated quests back out of the graveyard.

And watch them duke it out when both misfire.
>>
No. 65311 ID: 0f60d7

>>479617
People will tell stories of the day when the server broke down into internal civil war, and no one thread survived the onslaught.
>>
No. 65312 ID: 9677d0

Sounds good to me
>>
No. 65313 ID: 623deb

Rather than wasting people's time pressing buttons, why not just set the script to run on a timer every 2 weeks? I mean, there's no reason not to.
>>
No. 65314 ID: f0a931

>>479762
Then mods would have to be careful not to revive threads if they might be re-graveyarded before the author gets to bump them, or something like that
>>
No. 65315 ID: d6ae01

>>479762
It took like 3 years to convince Dylan to program a button. You really wanna go for a fully-automated script? :V

>>479769
If we went so far as to have a fully automatic script, it'd probably have some kind of thing to not move posts that have been recently moved or something


I'll be moving this thread to /dis/ and removing the sticky tomorrow.
>>
No. 65316 ID: aeaf2b

that is a creepy bird.
>>
No. 65317 ID: dba375

>>479933
So how many of us need to bug him until he finishes post editing?
>>
No. 65318 ID: f2c20c

Personally I think post editing is a bad idea for the quest format, at least, if anyone can edit their posts. That could lead to shenanigans and/or vote-counting errors.

I suppose it could be okay if there was only like, a 5-minute window to edit posts?
>>
No. 65319 ID: beeca1

>>479986
We have post editing in the form of deleting your post and reposting a fixed version.
>>
No. 65320 ID: d6ae01

>>480008
>>480024
A site-wide editing could be tricky to pull off, for various reasons and meta-reasons, but I'm still pushing for an easier method of post editing that uses the mod panel, rather than having to dive into the database and mess with the HTML by hand

Anyway, I think enough people have seen this, so TO THE DISCUSSION FORUM
>>
No. 65322 ID: d6ae01

Turns out there's a button to empty the reports table in the database, so when some jerk reports every thread with "1", they can be made reportable again.

It should be safer to report the OP of a thread now, since I will do that in response to report-spam. However, if a quest is revived, and then falls to the graveyard again, chances are you'll need to report the second post (or third, etc).
[Return] [Entire Thread] [Last 50 posts] [Last 100 posts]

Delete post []
Password  
Report post
Reason