item.pak not working

Every login try with the newest Item.pak data, come an Error Messenger like this:



cen someone help me ?

 

yeah u put it in the wrong place

the 2 locations r:
Data\USA\Items
Data\Items

1 of those is gonna give u an error, if that happens, put the old 1 back (if u didnt make a backup u need to repair) and put it in the other one ^^

and yes asankas guide is wrong

 

so not into Data/USA/Items?

and yes i got backup datas from system.ovr and all items datas

 

if u have a EU client, it goes into Data\Items and not Data\USA\Items

btw there r also more versions of items.pak. if u put it in the right place, u wont crash but it still might not work if u have a version for a different operating system. in any case try put it in the other place

 

it doesnt work with both places.

 

</3

By placing items.pak in data/items you'll get unable to initialize error (cuz i use small version of items.pak for 2.1). so keep advising without knowing it. If you've searched forum for similar errors back when 2.0 came to gamez you would've knew that some XP users wont be able to use it at all and that is OS problem and not items.pak's or place where you put it.

 

Dun worry I still <3 yous

 

so u're sayin for ppl who got aion EU we have to past it in

Data \ items ?

 

actually ive helped enough people with items.pak errors be4 and a lot of them could run it in Data\Items while getting crashes in the USA folder coz they had a different client from urs

yes i know XP SP3 people have issues, thats why i asked for his operating system

in any case if u cant get 2.1 to work in either of the places, try the 2.0 items.pak in my sig and see if that 1 works

and yeah if u have XP SP3 theres a chance none of them will

 

atm im using a windows 7 >.<

ill see what i can do to make it workin

 

32 or 64 bit btw and yeah i have windows 7 64bit and im using asankas atm although the 2.0 works just as well (just cant trade taha shield with it)

do u have a EU or US client btw? check in NCsoft launcher if it says EU/Europe after it

 

im using the 32 bits (i guess) and i have the EU client

 

i used large version for 2.0, thats why it works if you put it in data/items BUT even if you put it there there will be no effect on items restrictions because of load sequence of files in client (localized folders loaded after data/items and have priority over it).

 

check my 2.0 items.pak guide, download the win 7 EU client one and extract it to ur aion folder (it puts it in the right place for u)

and yes since u have a EU client it puts it in Data\Items and not the US folder, that will make it work

asanka the problem is that as u said that it laods a localized folder, but if he has a EU client and u put it in the USA folder...doesnt work does it xD

 

ill try it when i reach home

i hope i can use it

 

it loads localized folder anyway. And loaded folder depends on client loading options and our server uses CC=1 (country code = 1 (Usa), 2 (EU), 7 (Rus), etc). Also file/client have nothing to do with OS/CPU architecture and the only ones that had problem with it are some XP users or those who had outdated OS/runtimes.

 

that doesnt explain why US clients got crashes in the Data\Items and EU clients got crashes in Data\USA\Items when we ran 2.0. if it is as u said, it wouldnt make a difference

yes only XP users couldnt get it to work at all (actually in 1 place they could run the game without crashes but couldnt trade) BUT every OS got crashes when they put it in the wrong place

btw if as u said only XP users have problems, why is he crashing on windows 7? ^^ i know the 2.0 items.pak will work at the very least, i havent played around much with the 2.1 one

 

as i said: they either have corrupted client or oudated OS/runtimes.

 

its not a corrupted client (other than the items.pak itself) since they run the game just fine until they replace the items.pak and then start crashing

neither is it outdated OS if the game works until the point they replace the items.pak

 

that is a fail logic tbh. Originally all .xml files in client are stored as binary xmls, when you edit them you convert them to plain xml that require other tools from client/system to load them (not to mention they're many times larger than original binary xmls).