Server Disconnections: Patch 2.3.2

[Razmataz]

Greetings

I have looked around several threads, but the answers that have been availed are not what I need. My friend is hosting a Ascent 2.3.2 (Patch Update) server, sadly the repack is unknown since he re-entitled it.
Upon opening the realm, entering it to the character screen and pressing "Enter World", you will come to an abrupt halt, the loading screen finishing and you entering Azeroth -- the pause is for about 1 second, and the models still loading etc. After that, you will immediately disconnect. Every character, every account has this error and the realm is foreseeably going to be knocked out of the way.
The question is: How to fix this?
Currently, the theory is of the 2.3.2 models changing, and therefore not allowing the 2.3 ones to update. We have spawned some non-intractable game-objects, such as a boat at fray island (Do not go there, it wiped my characters out and recalled a summon).
We are both hoping from a reply on how to fix this. If anyone wants more details and questions to us, please post a reply on your inquiries so I can link it directly to Matt(y)

- In Gratitude
Raz.

[Kiev]

yeah what he needs to do is put maps in (i think) and make sure that all the config files are OK

[Razmataz]

Thanks for the response:
Matt(y)'s answer was that he thinks they're all correct; but he doesn't know how to check.
Enlighten him please.
- In Gratitude
Raz

[moreniu]

Having the same problem here.

[Steph]

Maps will be the same, there have been no new area additions.
DBC files may need updating, as yet I havent found an extractor and mafiaboy's dont work.
New LUA scripts, and DLL files, and a working 3004 release can all be found in my thread in my sig, all updated for the latest version of WoW.
Config files dont need any changes, there hasnt been a change to the standard config files in ages.

Hope this helps, basically, update your core, update all your scripts, and possibly, update your database. Most of these are found in the Steph's Corner thread below.

If my releases dont work, Gastric will probably be releasing his compiles soon, so keep an eye on his sticky thread at the top of this board.

[Le Froid]

Using new maps/dbcs?

[Ballwinkle]

havent tried yet :O

[Steph]

Primo, I have only released 3004, because everything after that is too buggy.

Just deal with it.

Bottom line: If you dont like other peoples compiles, compile your own. If you are too thick to compile your own, do me a favor and STFU and GTFO.

Thanks for the kind words everyone else. I know my server works, other peoples servers work - Knaur even uses my 3004 in his latest repack, and THAT works with 2.3.2.

2.3.2 support has been available since at least 2981, the problem is not my compiles, it's that some people are just too dim to put the right files in the right folders.

Im sorry for ranting, but I hate it when Im the main person at the moment compiling on this site for everyone to use, and some arrogant ungrateful leecher comes along and starts spouting rubbish.

If you dont like them, do it yourself.

[Steph]

LOL, thanks, you made me laugh with that.

[Razmataz]

Thanks for the responses, however, Steph, this problem still remains. I need to be able to message you privately to give Matt(y)'s MSN so he doesn't get spammed by other people; I hope this doesn't trouble you.

[Steph]

PMs are back on.

Use my latest repack, it'll sort out the crash.

[join]

well, so... how to get your latest repack?

[King Shaun]

Go to her thread, she releases all her threads there..

Steph's Corner - It will be near the top somewhere, because her stuff she releases is soo great!

Many kind regards,
Shaun.

[Steph]

lol, you are too kind.

[Ghosthopper]

Everyone is saying update this update that, probly they are right
however...What it could be is a zone spawning issue, what i mean by that is a .go object ID is bugging out and crashing your server, if you yourself added it then it will only work for you unless EVERYONE on your server downloads the "patch" even for one new .go object (made from scratch)
if they try and view it will load up basic interface (freeze for a second like you say) and disconnect

if your on ascent / mysql check all your spawn points of .go objects for anything abnormal or new. delete this - try again AFTER UPDATES and it should work correctly.
If not then here is a cookie :O
*cookie*