Senpuria

It would be helpful if you posted the revision of your core.

Have you put ad.exe in the main wow folder?

Maybe DB issue. Make sure creature is type beast and set flag for tame, also make sure creature doesn't have any weird unit flags to make it unattackable.

Until you find more information on how these attacks work, I'd suggest disabling custom channels. Having custom channels is not worth repeated attacks causing disconnections. If you know the core well, you MIGHT be able to write something blocking access to custom channels by level, however if people still want to attack the server using that exploit, I'm quite sure they would take the time to level up, just to attack it. Take a look at the quest, try doing the quest and see if there's any point in the quest if you logged out at a certain point it would force disconnect users, I wouldn't see this to be the case but its worth a try.

It does seem low, especially if your the only one thats farming. Although it does sometimes seem theres no ore in the area then you suddenly hit a load. If it continues like this try modding your conf and see if it evens it out. Otherwise you could just check the database and see if you have the correct amount of entries.

Just to be clear, wowhead duplicate node locations. So people may have spotted nodes in 600 different locations due to the random spawning on official servers, however they are far less nodes than this.

Well, as this is a database issue which is actually nothing related to mangos, I suggest signing up to the forums of the database you are trying to use. You'll probably find some information there, but I'll still try and sort your problem out. You must be executing the files in the wrong order, that thread will show you how to properly execute the sqls in the correct order.

I suggest if your getting that many errors when trying to update, drop your mangos database and create a fresh then follow this guide; http://udb.no-ip.org/index.php/topic,9543.0.html It should take less time to drop and re execute rather than trying to get rid of the errors

I have installed many many databases and that error is 100% wrong database selection when sql dumping

Developers are very busy with a lot of work so there will be a few exceptions where patches will be left to sit for awhile for other important patches. Plus all developers have real life's they have to get on with, can't spend 24 hours a day patching and developing mangos core. Rest assured though sooner or later all patches will be looked at and evaluated :]

Scriptdev2 looks like it working, it just seems theres a few missing script names in the database. Make sure you execute mangos_scriptname_full.sql into the mangos database, if that still doesn't clear it up you could always just pull out the entries manually and enter the script names.

Indeed, but you have to select the database in order for it to execute it into the correct database, otherwise it won't be able to locate. It looks to me like you've assumed if you have any database highlighted it will automatically place it into the mangos database anyway. If your using sqlyog, which you should if you followed the instillation guide, right click the mangos database to make sure you have that selected and click on import > from sql dump. Locate your corepatch and execute it from there.

Well I'm assuming RSA source is just mangos source with patches, so shouldn't be any problems there. Can you post a few of the errors your getting?

It looks like your trying to execute the character database into mangos hence *mangos.character_db_version* mangos. = the database you tried to execute into character_db_version is the table you couldn't find because it should be in characters

The git you pulled is for the mangos source code, this has nothing to do with the database. And the mangos sqls are only updates for the database, this will not populate it. http://udb.no-ip.org/ You can grab a full database from UDB, it should be 393, and you'll have to use the update packs to get to 399 which is the latest version.

Indeed where did you get your database from?

Sounds like you have no creature_template or creature in the database. Did you setup your database correctly?

Some good information here, sticky :]

I'm sure you can't actually target ghost gates, since they are designed to be invisible, hence not being targetable. However you can pull up the GO GUID using .gobject near and delete it from the world.

Ummm, you could probably use ".gobject near" next time you hit one of the walls. Its most likely a ghost gate that you can remove from the world. No idea why they would be there though lol. Hope this helps

My development server has crashed a few times, although when it crashes the log seems unusal and pretty much give no information, they all come to say this; Program exited with code 01. CRASH ON Wed May 12 04:24:52 EDT 2010 The program being debugged is not being run. BACKTRACE BACKTRACE FULL THREADS I've checked my logging settings and they all seem correct, is there anything I'm missing?

I don't think you can give arena points as quest reward, maybe if you can script an npc that gives arena points on quest complete with C++, or an item that gives arena points on use.

Hey everyone, I'm sure this is still a current issue and its also an issue on my 2.4.3 client also. Basically its not much of a "can you help thread" but more of a, would this work as a solution. I don't understand the code fully yet so I could be completely wrong and in most situations this would be rejected anyway lol. bool Totem::IsImmunedToSpell(SpellEntry const* spellInfo, bool useCharges) { for (int i=0;i<3;i++) { switch(spellInfo->EffectApplyAuraName[i]) { case SPELL_AURA_PERIODIC_DAMAGE: case SPELL_AURA_PERIODIC_LEECH: return true; default: continue; } } return Creature::IsImmunedToSpell(spellInfo, useCharges); } Now I'm (assuming) that the totem.cpp is making the totems immune to periodic damage and periodic leech spells, which it should. But the totem actually absorbs for instance, the direct damage of the moonfire. I think this may be because its classing moonfire as periodic damage spell (which it is) but not recognising the direct damage on spell cast. If I were to remove the case_SPELL_AURA_PERIODIC_DAMAGE: do you think it would then allow moonfires direct damage to be taken into account? Or even so, it would make grounding totem much easier to destory even for a temp solution?

Umm, I guess we can sticky this thread for now. Its probably the most up to date windows guide we have at the moment. Detail seems really good and I don't see why we can't have a few optional guides around anyway. Good work.

You can always do it from the database, I always find it much more entertaining than typing the command over and over again^^ If you want to take a look you'll find it in the npc_vendor template.