[REJECTED][Complete] Candy Bucket (Hallows End)[REJECTED]

Custom Code and Mods Custom Code and Requests
1

All the Candy Buckets in the Inns and Taverns

-----> Biohazard: HACK / INVALID: Method is WDB and should NOT be altered

UPDATE `quest_template` SET `Method`=0 WHERE `Title`=`Candy Bucket`; [/SQL]

2

ou sh*t man… what about IN ()? :smiley:

3

and how about

UPDATE `quest_template` SET `Method`=0 WHERE `Title`=`Candy Bucket`;[/CODE]

? /emoticons/default_smile.png

this is probably the easiest way

4

It might be HeidiSQL, I tried that and it updated just 1 record. lol

I removed ‘Limit 1’ /emoticons/default_biggrin.png

5

everybody started one time and everybody learns by his mistakes

6

Better to update a table by its index. So better to use IN.

7

Never EVER use name columns to defines stuff like this (lack of better words). Just go and write out all the quest IDs…

8

UPDATE quest_template SET Method=‘0’ WHERE (Title=‘Candy Bucket’);

try this /emoticons/default_smile.png

9

Wow… really?

No, serious. Really?

The only difference between your query and theirs is that you put brackets, which make no difference in this case, and you added quotes to the zero which are against our codestyles…

10

yes really, because

UPDATE quest_template SET Method=0 WHERE Title=Candy Bucket;

does not work for me. /emoticons/default_tongue.png

11
12

i just change the flag to auto accept and auto complete. Work perfect but i dont think its blizzlike

13

From what I gather, a more proper “fix”. Don’t know if its blizzlike but it works for me and I’m just a newb at this SQL stuff.

– Hippie Hallow’s End Candy Bucket fix

UPDATE quest_template SET Method=0 WHERE entry IN (12286,12331,12332,12333,12334,12335,12336,12336,12337,12338,12339,12340,12341,

12342,12344,12345,12346,12347,12348,12349,12350,12351,12352,12353,12354,12355,12356,

12357,12358,12359,12360,12361,12362,12363,12364,12365,12366,12367,12368,12369,12370,

12371,12372,12373,12374,12375,12376,12377,12378,12379,12380,12381,12382,12383,12384,

12385,12386,12387,12388,12389,12390,12391,12392,12393,12394,12395,12396,12397,12398,

12399,12400,12401,12402,12403,12404,12405,12406,12407,12408,12409,12410,12940,12941,

12944,12945,12946,12947,12950,13433,13434,13435,13436,13437,13438,13439,13448,13452,

13456,13459,13460,13461,13462,13463,13464,13465,13466,13467,13468,13469,13470,13471,

13472,13473,13474,13501,13548);

14

Last year (when I spawned the candy buckets) these quests were working fine, why aren’t they working anymore?

(And, if setting method to 0 is correct (which I doubt), the query “UPDATE quest_template SET Method=0 WHERE Title=Candy Bucket;” is fine. No idea what’s up with all the nitpicking)

15

hack == WRONG

Method == WDB field, should not be used!

16

Since when is it correct to use name params to change something?

17

Since it is retarded to list 120 quest ids when they all have in common their name.

18

I remember reading somewhere long ago we were never allowed to use name params in those cases but I guess you’re right. /emoticons/default_smile.png

19

Still this applys. Not really a clue what the correct fix would be, can someone enlighten me?

20

Figuring out what changed, core-wise, to the quests since one year ago (when this was working) might lead to a proper fix.