How to disable the auction? :scared:
thx !
Printable View
How to disable the auction? :scared:
thx !
manuel and live > pwAdmin / server configuration ...
Thanks for help-me =)
... i think best way is delete the npc with sNPCedit @ pwTools
Not remove npc. Disable the trigger/event instead :) (380 or 381 I don't remember well)
Does he rly mean the AH npc?
Or since it's 1.4.4 maybe he means the boutique biddinghall?!
Hmm... If it's the biddinghall in the boutique then Idk xD My players like it so I didnd't try to disable it.
+2 on what Rom said, I do NOT think it's a good idea to actually delete from NPCGEN. Rather, if there's something you do not want 'showing up' just disable it via a trigger link. :thumbup1:
open gdelivery config
find parametrs auction and change value to 0
is this issue still active? 144? 145?
Enable/Disable through pwAdmin / iWeb...
it is not working for 145... or just mine? have you try with 145? what client base do you use?Quote:
Originally Posted by 343
I don't remember if I tested specifically on 145, I will test, and post results later :wink:
Yea AH and turning it on / off via iWeb is working just fine...
What I did discover (that I'm not too happy about) is PTEMPLATE.CONF is not working AGAIN (like in 144)... I set it down to 'normal/official' rates; and still gained 50,000 EXP by killing a single lv1 mob as a lv1 char [when I should have gained only *5*](and instantly become lv14 character) B/S (or is it just me ?)
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...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}Quote:
Originally Posted by gunse
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)!
Just remove some new fields from some lists, change the offset of the elements.data and here you go!Quote:
Originally Posted by 343
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 :):Quote:
Originally Posted by Romulan
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:
Now that was easy: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
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 Romulan
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 ...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: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 :DQuote:
Originally Posted by 343
--- 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:
try this v62to63 i hope no error :laugh:Quote:
Originally Posted by 343
So far so good, what's the ruleset for converting v62=>v63 ??
when you join v63 with v62 you will get v63 with v62 data :cool:Quote:
Originally Posted by 343
Funny, here I was trying to 'figure out' [if there were] different 'commands' for sELedit conversion rules like "ADDLIST" instead of "REMOVELIST" /or/ "ADDVALUE" instead of "REMOVEVALUE", and all you did was a merge :lol:
I must inquire though. How exactly did you do this because once I started doing that (merge like you said), to see if I could produce a file exactly the same as yours, I could not... I did as follows:
-I took OFFICIAL pwi-v648 (v66) and downgraded it v66 => v63
-I then opened THAT (^) v63 (from official v66) for the merge as you stated you did
-I performed a merge with OFFICIAL pwi-v632 (v62) => (^) v63
I was thinking the result would == your file, but it !=. So, I am thinking you used different files, or different options? [the options I used were [X]Add New Items and [X]Replace Changed Items {I did not check remove missing items}]
Oh well, nonetheless I will post it here for share / evaluation (log included):
Here is the file I produced (and its merge log):
HERE you will find the elements.data AND the merge log
:D well this is the procedure:Quote:
Originally Posted by 343
1. open v63 data
2. click join to ... and pointed to v62 data
3. checked add new and change modify
4. waiting... and done
that's what i did, it can not be reversed, because when you reverse the procedure you will get contrary (v63 inside structure v62), remember that we try to avoid new data from v63 but we let new data from v63 still exist :D
-I took OFFICIAL pwi-v648 (v66) and downgraded it v66 => v63 <--- this step will produce v66 data that is incompatible with 632 clientQuote:
Originally Posted by 343
-I then opened THAT (^) v63 (from official v66) for the merge as you stated you did <---the v66 still there
-I performed a merge with OFFICIAL pwi-v632 (v62) => (^) v63 <--- which one did you open first? v62 or v63(66)? if v62 then you will get v66 data but if you open v63(66) first then you will get v62 data inside v63 structure :D
if you're trying to use the english PWI client, I have a tiny bit of advice to offer:Quote:
Originally Posted by gunse
if you noticed from anoter thread Istated I was using a PWI client. I actually was, with modded exe and the v63 vd files what I did was go into /config/elements/version.sw if you change that to 863 it loads up just fine
what i mean is no modded in client, use as it is, latest 648, just change the IP server, so what we need to mod is server side...Quote:
Originally Posted by Psytrac
Like I could have sworn I have told you before, then this is NO PWI client, since the game client executable and the .DATAs are the main comprise of the "client" (as a "whole")... If you replace the EXE and DATA's guess what, it's now CN client :ott1: Why else do you think if you try to use a v63 .data with real PWI .EXE it will immediately CRASH. Why do you think that if you try to use v62 or v66 w/ the CN .EXE IT will immediately crash. :wink:Quote:
Originally Posted by Psytrac
So although you may have started with a full PWI client, as soon as you replaced the EXE and the DATA's you effectively made it a CN client... Even though it's "in English" or because it uses our English .PCK's (it's still a CN client because it's the CN .EXE)
Hope this clears things up for you on that one :ott1::wink:
This would be nice... So we can just use official PWI data's and client =\ (but in reality I do not see this happening TBH)Quote:
Originally Posted by gunse
Useless to do that =/ Because this file is used only by the patcher.exe for the updates. Without to mention those files (version.sw) are inside every .pck alsoQuote:
Originally Posted by Psytrac
if that were true (and it's not) then you could put "1 0" in any client and it would run perfectly.Quote:
Originally Posted by Romulan
Very strange =/ I never had this issue since I'm a pw dev... And I never heard any people getting the same issue as you...Quote:
Originally Posted by Psytrac
apparently I'm specialQuote:
Originally Posted by Romulan
AFAIK all version.sw files (even the ones inside .PCKs that Rom speaks of) only affect patcher <.<
They do not hold any real significance to the client itself...