- MaNGOS ~Amber~ Releases 3.x.x

Hi. It seems that the problem is not related to compiling on 32bit or 64bit. I compiled rev. 10328 on a x32 system which starts normally, but after trying to enter world gives the same result, mangosd.exe crashes.

The last lines on the server before crash contains the following (at this time it was creating a new character):

PLAYER (Class: 3 Race: 4): Adding initial spell, id = 34082
Spell 34082 Effect0 : 6
Spell: aura is: 42
Aura: construct Spellid : 34082, Aura : 42 Duration : 0 Target : 1 Damage : 1
Spell 34082 Effect1 : 6
Spell: aura is: 140
Aura: construct Spellid : 34082, Aura : 140 Duration : 0 Target : 1 Damage : 15

Exept Elia950, does anybody else have the same issue?
Thanks for the replies.

Hi all.
I have some errors when I run AmberGUI.exe, it starts and then closes immediately
My system config: WinXP SP3, Framework 4.0, lib Microsoft Visual C++ 2010 (x86) 12.04.2010.
err.log

Code:

---

AmberGUI [v101 build 3h] using v10316
09.08.2010 9:31:44
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
  at AmberGui.guiForm.dbserver_stopped_checks()
  at AmberGui.guiForm.form_status_checks()
  at AmberGui.guiForm.mainForm_Load(Object sender, EventArgs e)
  at System.EventHandler.Invoke(Object sender, EventArgs e)
  at System.Windows.Forms.Form.OnLoad(EventArgs e)
  at System.Windows.Forms.Form.OnCreateControl()
  at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
  at System.Windows.Forms.Control.CreateControl()
  at System.Windows.Forms.Control.WmShowWindow(Message& m)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
  at System.Windows.Forms.ContainerControl.WndProc(Message& m)
  at System.Windows.Forms.Form.WmShowWindow(Message& m)
  at System.Windows.Forms.Form.WndProc(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

---

@feherlofia - Confirmed mangosd crashes when creating char or logging in on x86 windows running on a x86 processor . Hmm time to make a clean patch free version for testing...I'll let you know what I find...

@APEC - a setting in amber.ini points to a file that hasn't been created yet or doesn't exist, probably the edit file entry in tools. Try opening it in notepad and checking gui_conf_selected=0

Quote:

---

Originally Posted by shivajiva101

@APEC - a setting in amber.ini points to a file that hasn't been created yet or doesn't exist, probably the edit file entry in tools. Try opening it in notepad and checking gui_conf_selected=0

---

yep, it was necessary to change the value gui_conf_selected=0 (gui_conf_selected=4 it was after installing) and gui_opacity_val=0.99 to 1

reminds me never to use index value as setting, this should be filename text so if it's present on gui launch it's selected otherwise need to load a filename that exists to stop the null ref issue...but what I don't understand is why you would need to change the opacity value as transparency is working fine...not the only report so I will investigate further...

@feherlofia - VS2010 compiles on Win7 & XP x64 both crash on XP x86 @ char create/login using no patches except SD2, now building on x64 using VS2008 with no patches just SD2...

OMG VS2008 core works! WTF! Ok last check is VS2008 on Win7 then I'll build latest version as an update after I've checked website/gui. I'll be really pissed off if VS2008 core compiles on Win7 crash because I've just loaded it on my dev lappy...grrr

Final piece of the puzzle narrows the bug to VS2010 as VS2008 works on Win7. At least I have a baseline for what currently works to keep x86 users happy, now when xeross updates his public branch we have the ingredients for an update...

nice job.........

was getting AH issues in last 2 builds (display from minimanager of AH would bring up errors sugesting the tables didnt exist)

rolled back to
YTDB 0.13.5 CS556 + SD2 R1741 + MaNGOS 0.17.0 v10199 Full
and alls sweet , ill hang for the outcome of the problems others have had...

anyways my issue with all the builds is that when i use minimanager and try to send ingame email (to send gold etc) or to edit characters data i get an error stating i have no permission to use.

i am logging in as root admin..

any ideas guys and girls ?

Quote:

---

Originally Posted by darrellmangos

nice job.........

was getting AH issues in last 2 builds (display from minimanager of AH would bring up errors sugesting the tables didnt exist)

rolled back to
YTDB 0.13.5 CS556 + SD2 R1741 + MaNGOS 0.17.0 v10199 Full
and alls sweet , ill hang for the outcome of the problems others have had...

anyways my issue with all the builds is that when i use minimanager and try to send ingame email (to send gold etc) or to edit characters data i get an error stating i have no permission to use.

i am logging in as root admin..

any ideas guys and girls ?

---

go into mysql and change your admin status from 3 to 5

Hey thanks for the response. It made me think about what all I had actually changed and I decided I was not really sure. I uninstalled the 3.3.2 I was running to start over then decided to try the newest updates for 3.3.5 instead. This time I had a better idea of where to find the files to change and once again RTFM. The whole thing runs great now and everyone can log into the LAN just fine. Thank you again for doing this, we are having a great time with it.

Quote:

---

Originally Posted by kubilius

go into mysql and change your admin status from 3 to 5

---

thanks for that , all good now..
although i was sure before i had my admin at 4 and it worked okay.. oh well maybe i was mistaken

please someone make vido tutorial or detailed guide for this repack?

Thanks shiv seems that ahbot is the problem. New OS, Clean Amber, NOT running the ahbot = 27ms this is good.

Yes AHBot patch is going thru some major changes, xeross had a vacation from updating his branch which caused problems when the devs decided it was time to recode the unmanaged const char* to its managed form making prev methods redundant, on the upside this bring's most of the flaws to light with the patch as it's scrutinised by other programmers and takes us a step closer to the patch being integrated into the core...can't wait for that! Cyberiums work to remove the dependancy on an actual character for the patch to function is the biggest leap forward I've seen in years towards Vladimir's stringent requirements for inclusion of this non blizzlike patch.

Well I have no problems with the ah bot running under xp.
I hope shiv keeps it because it's very useful in a small pop server like mine ;)

BTW if you you get a chance look in to adding shaz armory supposed to work with 3.3.5a ;)
Also you might consider updating the web page using mangos enhanced ver 2.0
I have replace it with the mangos web with very few problems ;)

Quote:

---

Originally Posted by nighthawk1000

Well I have no problems with the ah bot running under xp.
I hope shiv keeps it because it's very useful in a small pop server like mine ;)

BTW if you you get a chance look in to adding shaz armory supposed to work with 3.3.5a ;)
Also you might consider updating the web page using mangos enhanced ver 2.0
I have replace it with the mangos web with very few problems ;)

---

The problem I have is lag on the server thats it. The Website in Shivs pack is good. Everything is good But.... when AHBot is active lag goes through the roof...Nighthawk1000 what are your settings at? can ya post them? maybee i have mine set to high in the db...

Only major issue with AHBot in those releases is the sheer amount of mail for expired items coming back at the ahbot char which I think has been supressed in cyberiums version as well as the need to create a specific ahbot character for the bot to work, meanwhile xeross is waiting for more feedback before adopting the code changes, leaving me wondering if I should risk a release on cyberiums patch or not...