CowKing ???

Mu online season 21 - grand opening

samhag

Dedicated Member
Dedicated Member
Jul 31, 2008
213
0
42
Ive got the following error on my M2 server- CowKing process error.

Anyone know what it means and how to fix it ??
I did change a couple of things yesterday but ive been to sleep since then and i`ll be buggered if i can remember what :dunce:
 

samhag

Dedicated Member
Dedicated Member
Jul 31, 2008
213
0
42
depends on what you wanted to do..

Really just wanted to know if anyone knew what the error meant.
The last thing I can remember changing was adding @key7 and @key8 custom commands which worked fine, but removing them didnt get rid of the CowKing error so im guessing it wasnt that that has caused it.
 
Upvote 0

azzi

Golden Oldie
Golden Oldie
Aug 16, 2005
1,662
19
175
Its either a function uve made . Or its a Mob. So have a look through and check them over.
 
Upvote 0

samhag

Dedicated Member
Dedicated Member
Jul 31, 2008
213
0
42
Its either a function uve made . Or its a Mob. So have a look through and check them over.

Seems to be a mob, i did add some recently, ive just stopped them spawning in TBL_MONGEN and the error has gone. Not looked at why yet but will report back when i find out why.

Thx for ya help.
 
Upvote 0

Far

tinmymouthpl0x
Staff member
Administrator
May 19, 2003
20,683
34
3,289
520
try removing the mob from your mongen like samhag did...
 
Upvote 0

Hone

LOMCN Veteran
Veteran
Loyal Member
Jun 10, 2009
270
5
45
Melbourne, Australia
you mean cowking? i thought it was a mob at first as well but it isn't, nothing named 'cowking' in my files at all.

what it is i think is just a name for an error which is caused by having a mob trying to spawn in your mogen which doesn't exist in your monster db.

i think anyway, im still trying to find out for sure
 
Upvote 0

Killmaster

Legend
Legendary
Golden Oldie
Loyal Member
Nov 13, 2003
3,967
27
274
I remember looking at the source codes and there was a thing about CowKing... it was a mob. I'm guessing its something to do with an attack of some sort.
 
Upvote 0

paul.obrien

LOMCN Veteran
Veteran
Aug 28, 2008
453
4
45
i think you have sussed this now.
You have the mob cowking in your mTBL_MONGEn table but have forgotten to add it in to your TBL_MONSTER table as well

You will need to add the mob to the monster tbl and reboot the server
 
Upvote 0

Hone

LOMCN Veteran
Veteran
Loyal Member
Jun 10, 2009
270
5
45
Melbourne, Australia
i think you have sussed this now.
You have the mob cowking in your mTBL_MONGEn table but have forgotten to add it in to your TBL_MONSTER table as well

You will need to add the mob to the monster tbl and reboot the server

Well no that's the thing, I've searched both my TBL_MONGEN and TBL_MONSTER and there is nothing called CowKing. I've also searched my server files and the only thing it finds is the M2 log being spammed with the error...

Killmaster said:
I remember looking at the source codes and there was a thing about CowKing... it was a mob. I'm guessing its something to do with an attack of some sort.

I dont think it's a mob at all...I think its a generic error which occurs when you have a mob (any mob) in your mongen which isn't in your monster db.

i.e. the mongen is trying to spawn a ZumaArcher20 in BDD but there isn't a mob called ZumaArcher20 in your mob db.

Whether this is true or not I dunno, I did find ChestnutTree1 and 2 in my mongen, which aren't in my db, so I deleted them and the error still shows... and I can't find any other differences between the 2 tables, but then there isn't a way of comparing them other than by eye as far as I know :/
 
Last edited:
Upvote 0

Hone

LOMCN Veteran
Veteran
Loyal Member
Jun 10, 2009
270
5
45
Melbourne, Australia
Tried that, now I know it's got nothing to do with a mob called CowKing. I've narrowed it down to the tbl_monster as I just uploaded an old version and it's stopped spamming errors. Just need to work out what's wrong with my mon db now..
 
Upvote 0

hustler

Banned
Banned
Veteran
Jun 6, 2009
570
30
115
Compare the two and see what you've changed recently to get that error. It worked fine last night, must've been somthing you recently added.
 
Upvote 0

Hone

LOMCN Veteran
Veteran
Loyal Member
Jun 10, 2009
270
5
45
Melbourne, Australia
no the mon db works fine, (the new one we added last night) but it gives the error on the m2.

When I just changed it to the basis db which comes with standard 2.3 files the error stops.

Dont really see how im gonna go about comparing them tho cos there's like 10000 odd spawns to look through lol
 
Upvote 0

hustler

Banned
Banned
Veteran
Jun 6, 2009
570
30
115
It worked fine last night though didnt it? It's somthing you or me added recently, perhaps them numas?
 
Upvote 0