Disable Auction ????

Quote:

---

Originally Posted by gunse

i'd have AH trouble before because of elements.data issue, and i experience 50k exp because of server elements.data has damn EXP mobs 10k times, double multi check your server elements.data, never trust published elements.data, some mods are crap...

---

OMG THANK YOU for that... Last night I was SO busy, here was my mistake of the year! IDK why but I was looking in elements at the EXP chart - like someone modified IT :lol::lol: Yea, that mob is giving me 50k because someone must have messed with the exp of the mob in elements.data -- now it's just too bad I deleted my working VM last night in a //rage <.< {*sighs* re-installing now}

So your AH issue has since been resolved ?

Yea, I'm going to have to find a way to 'convert' the OFFICIAL PWi elements.data v66~v63 (so we can have a real VIRGIN elements)!

Quote:

---

Originally Posted by 343

Yea, I'm going to have to find a way to 'convert' the OFFICIAL PWi elements.data v66~v63 (so we can have a real VIRGIN elements)!

---

Just remove some new fields from some lists, change the offset of the elements.data and here you go!

Quote:

---

Originally Posted by Romulan

Just remove some new fields from some lists, change the offset of the elements.data and here you go!

---

Thank you greatly Rom, I have been in love with 126/136 so much that I am honestly not really familiar with some of this new shit :):

This was also my first time creating a 'ruleset' for sELedit so that this could be done - I think I did a pretty decent job for my first time and on a whim :):

For anyone else that would like to create their own VIRGIN PWI official elements downgrade create a rules file for sELedit using the following info:

Code:

---

##############################
#### RULES FOR v66 => v63 ####
##############################

REPLACEOFFSET:0|3F-00-00-30-AD-F5-DA-4F

REMOVEVALUE:38:266
REMOVEVALUE:137:5
REMOVEVALUE:137:6
REMOVEVALUE:137:7
REMOVEVALUE:137:8
REMOVEVALUE:137:9
REMOVEVALUE:137:10
REMOVEVALUE:137:11
REMOVEVALUE:137:12
REMOVEVALUE:137:13
REMOVEVALUE:137:14
REMOVEVALUE:137:15
REMOVEVALUE:137:16
REMOVEVALUE:137:17
REMOVEVALUE:137:18
REMOVEVALUE:137:19
REMOVEVALUE:137:20
REMOVEVALUE:137:21
REMOVEVALUE:137:22
REMOVEVALUE:137:23
REMOVEVALUE:137:24
REMOVEVALUE:137:25
REMOVEVALUE:137:26
REMOVEVALUE:137:27
REMOVEVALUE:137:28
REMOVEVALUE:137:29
REMOVEVALUE:137:30
REMOVEVALUE:137:31
REMOVEVALUE:137:32
REMOVEVALUE:137:33
REMOVEVALUE:137:34
REMOVEVALUE:137:35
REMOVEVALUE:137:36

---

Now that was easy:

http://www.stopgettingcheated.com/im...asy-button.jpg

This rule will work only with elements.data v66. You will need to edit the rule again if there is a new version of elements.data ... Btw I changed some other offset also just to be sure...

Code:

---

REPLACEOFFSET:0|3F-00-00-30-A9-4E-58-4F
REPLACEOFFSET:20|DD-89-76-AB-0A-00-00-00-F2-23-D9-94-E5-31-D1-94-E5-31-AA-4E-58-4F
REPLACEOFFSET:100|9F-67-35-EE-51-00-00-00-21-E6-8C-D4-2A-FA-04-27-A8-D7-DA-AA-CC-9D-D4-B8-30-FD-3C-AD-CC-BA-24-54-D6-1F-53-3C-E2-50-FC-5E-21-E6-A8-E1-67-F2-0C-27-C4-82-EE-AE-00-8C-51-35-30-ED-3C-8D-39-CE-18-48-D3-42-46-2D-87-35-D9-77-44-9F-D5-59-63-FA-70-1F-AC-FA-C2-B2-74-44-45-F9-FC

---

Quote:

---

Originally Posted by Romulan

This rule will work only with elements.data v66. You will need to edit the rule again if there is a new version of elements.data ... Btw I changed some other offset also just to be sure...

Code:

---

REPLACEOFFSET:0|3F-00-00-30-A9-4E-58-4F
REPLACEOFFSET:20|DD-89-76-AB-0A-00-00-00-F2-23-D9-94-E5-31-D1-94-E5-31-AA-4E-58-4F
REPLACEOFFSET:100|9F-67-35-EE-51-00-00-00-21-E6-8C-D4-2A-FA-04-27-A8-D7-DA-AA-CC-9D-D4-B8-30-FD-3C-AD-CC-BA-24-54-D6-1F-53-3C-E2-50-FC-5E-21-E6-A8-E1-67-F2-0C-27-C4-82-EE-AE-00-8C-51-35-30-ED-3C-8D-39-CE-18-48-D3-42-46-2D-87-35-D9-77-44-9F-D5-59-63-FA-70-1F-AC-FA-C2-B2-74-44-45-F9-FC

---

---

no need rom, trust me :cool:

Quote:

---

Originally Posted by 343

OMG THANK YOU for that... Last night I was SO busy, here was my mistake of the year! IDK why but I was looking in elements at the EXP chart - like someone modified IT :lol::lol: Yea, that mob is giving me 50k because someone must have messed with the exp of the mob in elements.data -- now it's just too bad I deleted my working VM last night in a //rage <.< {*sighs* re-installing now}

So your AH issue has since been resolved ?

Yea, I'm going to have to find a way to 'convert' the OFFICIAL PWi elements.data v66~v63 (so we can have a real VIRGIN elements)!

---

yep resolved with fully 100% latest PWI elements data :thumbup: that's why i wonder if i can change my gs structure to read latest data then we can use latest client... we can use 648 client with peace ... so relief ...

That would be cool as shit !

ADD: My next question:

I see there aren't much differences between v62 and v63, how could we convert v62 => v63 ?

Quote:

---

Originally Posted by 343

That would be cool as shit !

ADD: My next question:

I see there aren't much differences between v62 and v63, how could we convert v62 => v63 ?

---

62? do you mean from 144 to 145? let us try bro :ott:

Actually v62 is also all the way up to the Imperial Fury update (including 1.4.5 Descent*)

I know because I took VIRGIN official PWI files from pwi update patch v632 (v632 was the last version before "Imperial Fury", v639 IS "Imperial Fury" where PWI started using v66)

I almost see this as being necessary to figure out because I just tested my whole v66 => v63 and although it does 'work' it looks like there have been several 'changes' which WILL 'break' things (ie. the model of the GM weapon has changed, and now produces this graphical error, among others - and there's no way I would go through manually to fix any and all flaws. It would be best to figure out v62 => v63 :wink:)

(screenshots to come)

Quote:

---

Originally Posted by 343

Actually v62 is also all the way up to the Imperial Fury update (including 1.4.5 Descent*)

I know because I took VIRGIN official PWI files from pwi update patch v632 (v632 was the last version before "Imperial Fury", v639 IS "Imperial Fury" where PWI started using v66)

I almost see this as being necessary to figure out because I just tested my whole v66 => v63 and although it does 'work' it looks like there have been several 'changes' which WILL 'break' things (ie. the model of the GM weapon has changed, and now produces this graphical error, among others - and there's no way I would go through manually to fix any and all flaws. It would be best to figure out v62 => v63 :wink:)

(screenshots to come)

---

owh i see, ok ok understood, ok let us try, i have 632 patch also, i'll try, yes you are right, elements.data uses graphical thing on another files, that's why 645 converted file only work on 645 client and 648 converted only for 648 client :D

--- 5 minutes later ---
there is no command to insert list or add list ... should we add it hard coded?

Here are a few screenies:

As you can see (from looking at the sELedit loader configs) there is only one real difference between v62 and v63 (other than offsets), and that is, in v62 there are 150 lists, in v63 there are 151 (so to convert v62 => v63 we would surely have to add this list [and I don't see any documentation on how to ADD lists on a 'conversion' in sELedit {only how to REMOVE =\}])

Oh and here are the initial graphical atrocities that I noticed after converting v66 => v63:

So if I noticed that many (2) at the log in screen alone, I could only imagine how many other problems there will be <.<

Lol, nice gfx on ur sword 343, if it is gfx.

No, it's elements related (read above :ott1:)

Well it IS gfx, but it's not gfx because it's elements related

If I am making any sense @.@

:lol:

Quote:

---

Originally Posted by 343

No, it's elements related (read above :ott1:)

Well it IS gfx, but it's not gfx because it's elements related

If I am making any sense @.@

:lol:

---

try this v62to63 i hope no error :laugh: