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 - Temptation_Town
1
« on: March 18, 2015, 10:16:03 pm »
CharSections.dbc
I doubt that all 21 can be unlocked at the same time, probably you will need to remove some default skins.
2
« on: March 13, 2015, 02:24:18 pm »
The 4.3.4 client doesn't read patches from the Data folder that are higher than 15595.
No, no no no, that's wrong.
I have a patch named wow-update-base-200000000, no problem with that
Be sure you have applied max limitation fix on your wow exe, you can do it manually in exe but you need the offset, you can find this on ownedcore, stoneharry thread.
Yeah, I was thinkin the same. It's just her wow.exe wasn't patched for that.
3
« on: March 13, 2015, 03:59:11 am »
Ok now I'll bring some constructive stuff in this thread.
Kilian, here is the screen of my Data folder. All that stuff work fine.
So check again your patch names, they must be correct.
4
« on: March 13, 2015, 03:52:10 am »
Wanna bet? You'll teach me LightIntBand stuff if I'm right. Bet what? That the SoundCache-Patch-15595.MPQ won't fix it?
Sure because I know it will.
Bet about custom patches from Data folder. So? Ofc they must be named correct, that's why I told him to screen his folder, he might fail with patch names.
5
« on: March 13, 2015, 03:41:01 am »
The 4.3.4 client doesn't read patches from the Data folder that are higher than 15595. And lower patches don't seem to work for certain things like custom items. I'm not sure how you got yours working differently but I've never heard of it.
As soon as Killan puts the patch into the Cache folder, it will work 100% as always. Wanna bet? You'll teach me LightIntBand stuff if I'm right.
6
« on: March 13, 2015, 03:22:20 am »
Patches from Data folder work fine. No need in Cache folder.
They don't work fine... It needs to either be in enUS folder or Data/Cache.
There's nothing wrong with his client either. This is normal.
There is no need in Cache folder. Data works fine. As I said I had same errors when I launched patches with non-English client. Switch to English helped me. Lets wait that guy and his answer about client language.
7
« on: March 13, 2015, 03:12:25 am »
Still can't get it to work... atleas the client doesnt fuck up anymore..
Ive named the patch from 15600 to 15630 and none of it work...and 12000 worked on the windows client i remember
Im clueless  For Cataclysm patches, typically you'll want to place them in your Data/Cache folder. It doesn't read properly from the Data folder alone. So go into the Cache and replace SoundCache-Patch-15595.MPQ.
Patches from Data folder work fine. No need in Cache folder. I wanna see his client, I'm sure it's non-English client and this is the core of problem. I had same error too with non-English settings.
8
« on: March 13, 2015, 12:26:53 am »
Still can't get it to work... atleas the client doesnt fuck up anymore..
Ive named the patch from 15600 to 15630 and none of it work...and 12000 worked on the windows client i remember
Here is my wow.exe, uploaded it here http://www.mediafire.com/download/10u45 ... atched.exeWe aren't telepaths here, so better make a video or some pack of screenshots with your Data folder, Login Screen, your patches (opened in MPQ editor) and I'll try to check that stuff.
9
« on: March 12, 2015, 07:20:14 pm »
My client IS 100%...the patch worked once but after i restarted wow it was broken
I got that torrent but exe missing  Then you are doing something wrong. client/Data/patch-15600 and higher value.MPQ That's how it must look. Btw it can also be language problem, I had it before. Patching requires same version as client. Get En client and the same En DBC for your patches. And your new language stuff (EnGB folder) must be fully downloaded too.
10
« on: March 12, 2015, 07:07:19 pm »
Sorry I'm late. This is a little known issue with 4.3.4 modding. Don't ask why, I have no idea...
Certain patches, including my patch, will destroy a Windows client. If you want to mod 4.3.4 safely you're going to have to use the Mac client, which runs 100% fine on Windows and completely eliminates the client corruption problem.
If you continue attempting to use the Windows client, it will break every single time.
Get the Mac client here: http://www.mediafire.com/download/wlbpg ... PB.torrent
Also sorry this ruined your setup. But if you wanna mod 4.3.4, you're better off now. Actually... this isn't completely true. My Win 4.3.4 works fine with all patches. Kilian, your problem was in your client. It wasn't fully downloaded, thats why it required that "archive data". It was said many times here - modding requires complete client.
11
« on: February 04, 2015, 08:40:58 am »
Nice release and on 3.3.5a?  This is not 3.3.5 thread. I dunno why, but I have an error "Cannot stream required archive data. Please check the internet connection." - where is the problem? This is lang problem I guess. Use English client (or change it to English in Options). Or you have placed patch in the wrong folder.
12
« on: January 31, 2015, 07:42:40 pm »
Hmpf? If you still don't get it I don't have any problem with this . I have transferred BE via this method to Alliance more than year ago and it just worked as it was supposed to, and keeps working until now. Later I have also transferred all other originaly Horde races to disable interfaction PvP on my RP server, but situation "original Horde races kept in Horde, BEs transferred to Alliance" was tested and worked. I have also never had any problems with character creation screen, but like I said, my LUA files are edited (to be more accurate, I use one of the Mordred's systems).
I just don't know wtf is going wrong here. Everything worked for me on 3 different TC2 versions for nearly a year and a half. I had a few glitches, but all were caused by my stupidity when I have uploaded wrong outdated DBCs to core. All my BEs were created with Alliance side, but a lot of my other Horde chars were created before I migrated them all to Alliance too (but they were moved all together). I still can't find out if Renan is in situation in which my characters never were or if we just missed something somewhere. I have it worked in the way I described in my first post here. Too many words, just add here your CharacterCreate.lua, CharacterCreate.xml
13
« on: January 31, 2015, 05:41:22 am »
My tests were run on characters made before the changes and characters made after the changes. I discovered that they aren't friendly all the time, and in fact will revert to attackable yet friendly on zone change or relog. I've been solo testing this as I have nobody to test this with, but I figured since it classifies me as alliance client-side and server-side that it'd be fine to trade.
Make 2 windows of wow, tp them in the same place and try to invite BE char in human's group. Make a screenshot. Make sure that interfaction interaction (party/trade) is disabled in worldserver.conf. That would nullify all tests. If it's all ok, and they can be in the same group, then check again character create screen. Are BE there? Same questions to Amaroth.
14
« on: January 30, 2015, 09:53:52 am »
I guess I managed to somewhat get it to work, but now I guess I need to manually adjust the reputations of every Blood Elf so that they're of the alliance. When adjusted to exalted with alliance, I could interract with NPCs and everything, but I couldn't actually see their reputations in the rep window and I was friendly with horde (likely due to default reputation). Reputations and NPC interaction are the most simple things here. Did you check player interaction? Can you invitetrade with human, dwarf and others with your BE char?
15
« on: January 28, 2015, 04:32:05 am »
The elf characters had an alliance flag but were friendly to horde, hostile to alliance, but the teleporter registered the elf as alliance and offered to port to alliance cities.
Not sure how to fix it so that the elf players are friendly to alliance and hostile to horde.
You will not fix this. Go make better use of your time.
|
Show Posts