Modcraft - The community dedicated to quality WoW modding!
Content creation => Level Design => Topic started by: Zim4ik on July 12, 2011, 07:09:30 am
-
Okay, i`ve never have this error with nogg-it 104 before!
http://pastebin.com/3cYUJsmV - link
Please, help me. i dont know whatta sh is going on with my noobit)
-
World 1: has no WDT file!
You created a new map and noggit cant find the WDT file.
Take a look taht the WDT is also in your Client/world/maps/World1/ folder named world1.wdt
And if your Map is called World 1 with an space between the world and the 1 then rename all your stuff. No spaces in map names!
If you have renamed and have a wdt inside your folder then the following could help:
An old version of noggit did not load wdts direct from disk. You had to put the wdt with the fitting path into a MPQ and put this into the data folder.
-
Umm... All what i`ve added into map.dbc its Gilneas. ;)
I think that World 1 its a column which have 1id. Its an Kalimdor. But i try to do what u say.
-
That a map shows in noggit you need.
1. A modifyed map.dbc with the new entry.
2. The world/maps/yourmap folder with a WDT file and all the ADTS activated in the WDT.
All this stuff should be located inside the wow client you use for noggit direct inside folders or in your project directory. If you set one in the config file.
And then test the WDT not load problem or just use B22 of 120 from beta board. Or what did the 104 what the 120 dont do right?
-
120 crashes gilneas city districts WMO`s. 104 works well with them.
-
And what meen crashes ?
And what 120 :)
-
SIGSEGV error in log before noggit 120 rev is crashed. sorry for my bad English.
-
And again what version B22, B21, B20 .....
-
B21, B20
B22 dont see my maps because i`ve got the russian client type.
-
Could you uppload me your ruRU folder?
-
Umm.. no)
My internet connection is sucks for now. i can upload to you Map.dbc or smth)
-
The problem is that in the en and de version everything works fine. So i must test the problem with an russian client to find out if its a localisation problem.
-
Try to change it with your methods and test it for noggit 104
-
And the last 5 posts are why I want you to never refer to 120 again. Thanks.