Send me that itemadd.ini =oQuote:
well they just use itemadd.ini in the unique sources, but binaries you need the table cq_itemaddition
3rd Socket issues
10/21/2009 16:03
~*NewDuuDe*~#16
10/21/2009 21:03
~Yuki~#17
no me !
10/22/2009 00:41
raidenx123#18
well i just released it....
10/22/2009 01:04
Illustria#19
Alright folks heres what i did, i coded in soc3 into the source, properly defined in all the same places as soc1 and 2 configured soc3 to work the exact same as those with the added code to make 3rd sockets harder to get with luck of a met or db in tc or market, as well 3rd socket for talismans are set to 100k progress points. I have added in the database the soc3 variable, and inside the item dat file i have added the extra variable for the 3rd socket. Anyone else think of what im missing?
10/22/2009 01:18
_tao4229_#20
Making the client interpret the information you've added <_<?Quote:
10/22/2009 01:36
Illustria#21
I was hoping that was a simple matter of adding the extra variable to the itemadd.ini. Care to expand? I gotta learn and hopefully write everyone a tutorial.Quote:
10/22/2009 01:38
raidenx123#22
itemadd.ini is for the extra stats when you have a + item, not a socket.
10/22/2009 01:41
Illustria#23
Ah alright, so ideas on what needs to be done? I think the only issue im having left is with the client side.Quote:
10/22/2009 02:22
_tao4229_#24
You'd have to essentially reprogram Conquer.exe to handle the packets differently, graphically output the extra socket, etc.
Unless you know a great deal of assembly (and have a few straight days on your hands to find out addresses, and add in the necessary code, it's quite impossible)
I'll spare you from the fail.
Unless you know a great deal of assembly (and have a few straight days on your hands to find out addresses, and add in the necessary code, it's quite impossible)
I'll spare you from the fail.