This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Ayos
Pages: [1]
1
« on: March 11, 2020, 04:18:19 pm »
Is it possible to downport a model file from WoD to Vanilla?
Or maybe WoD->WotLK->Vanilla in 2 steps?
I just need an m2 headgear which is bugged/unfinished in vanilla but properly done in wod.
2
« on: March 11, 2020, 04:14:58 pm »
The problem was, that the vmangos (nost) core only supports spells with entry (id) up to 35.000. This can be changed in the core.
3
« on: October 08, 2019, 05:46:50 pm »
Hi!
My issue is, that if I copy an existing spell to a new ID, it will properly show ingame, even if I add it to a talent tree, but when I try to cast it, it will cast infinitely. The cast stops at the end of the cast bar while the bar shows the proper spell name aswell.
Not sure why is that, but I'm clueless at this point for sooo long.
Here is what I have done so far:
- Copied the spell to a new id in the spell_templates database table
- Copied the spell to the a new id in the Spell.dbc (same ID as in the database)
- Also added it to the SkillLineAbility.dbc
- Added the new Spell.dbc & SkillLineAbility.dbc to the server's dbc files, and into my client patch MPQ
- Server restarted, client cache cleaned, the spell shows properly just won't finish casting
If somebody did something like this before, any help would be highly appreciated!
5
« on: February 18, 2019, 05:15:56 pm »
Hi!
A few weeks ago I was looking for a vanilla exe with glueXML+frameXML protections removed, but it seemed like that its nowhere to be found in the entire internet, so I made one myself.
If anyone is interested, I attached it. Enjoy!
6
« on: November 03, 2018, 02:55:56 pm »
Hi!
I would like to remove the frameXML protection from the 1.12.1 wow.exe.
I found modded exes on different sites, but those had only the glueXML removed,
so I would like a tool which can patch an exe, or an exe that has frameXML checking already disabled.
I think the name of the tool was wow_unsig(5875).zip, but I cannot found it anywhere.
Thanks in advance!
7
« on: September 11, 2018, 12:45:53 pm »
Hi!
I've made a classic server with CMANGOS 1.12.1 which I only want to customize on the Server/Database side if possible. And I managed to do a lot of things already, including talent point alocation rewamp, but I wasn't able to find where to change the minimum level when the player is able to open the Talent Panel.
My question is:
How can I make the talent panel appear at level 1 without (hopefully) editing the client itself?
Or there are no methods for that, where to look at the mpqs?
Thanks in advance!
8
« on: August 04, 2013, 12:16:56 pm »
My problem was almost the same as yours. The client always crashed when i used my 64x64 map, but when i made a 63x63 version (still dont know why), the crashes disappaered. So just try to cut the outter lines of your map.
9
« on: July 13, 2013, 04:25:02 pm »
So, i recreated the whole map again with a different adt template from this site and still crashing, but this time from this:
ERROR #132 (0x85100084) Fatal Exception
Program: D:JátékokTauri WoWWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B4D14
The instruction at "0x007B4D14" referenced memory at "0x00000071".
The memory could not be "read".
I hope this is not related to the fact that i use a full 64x64 map... this size is necessary for my project.
Any idea?
10
« on: July 04, 2013, 07:17:18 pm »
I hope you can find some solution..  it's really annoying.
11
« on: July 03, 2013, 02:18:32 pm »
Hi! I just started a project a few days ago with a concept that requires a full sized map. Everything worked fine with a small testmap before, but when i started a new full-sized map, it even crashes my wow client and noggit at totally random spots.
Here is the crash report:
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: D:JátékokTauri WoWWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007B4D61
The instruction at "0x007B4D61" referenced memory at "0x00000071".
The memory could not be "read".
Yesterday it was "0x004057FB" read "0x00000004" but i think somehow i fixed that, but then this new error appaered instantly.
Any idea?
Pages: [1]
|
Show Posts