This script checks whether the user's active mode setting is correct, and warns the user if not. All IP/port pairs are checked only once, and local (RFC1918) IPs won't be checked. PXWSA.DLL must be in the scripts folder.
http://ptxscriptdb.psycho-chihuahua.net/download.php?view.85
where can i get the DLL file?
Thanx
-click- (http://www.thewildplace.dk/site/download.php?list.11)
Blimey that was quick!
Thanx
Bastya,
your script asks for a Pxlua.dll...
All i done was to copy the pxwsa.dll to the ptokax script folder and start the script. Did i miss something?
Thanx
QuoteOriginally posted by yoonohoo
Bastya,
your script asks for a Pxlua.dll...
All i done was to copy the pxwsa.dll to the ptokax script folder and start the script. Did i miss something?
Thanx
If no path is specified for the pxwsa.dll in the script.
It should be located in the ptokax folder (same folder as ptokax.exe and pxlua.dll).
btw. you need a ptokax version greater or equal to 0.3.3.2
I have the pxwsa dll in my scripts folder, and works that way too. Maybe this is a PtokaX version issue, since there is NO pxwsa.dll in my frmHub:GetPtokaXLocation(). :P
Bast, maybe it would be better if all ppls where useing the same folder for libs. Else i guess a lot of ppls will be confused about that.
Maybe restricting the lib folders , to only one folder would be a good idea. For example /ptokax/scripts/libs.
i made a new folder in ptokaX root called lib (../lib used in scripts)
QuoteOriginally posted by bluebear
Bast, maybe it would be better if all ppls where useing the same folder for libs. Else i guess a lot of ppls will be confused about that.
Maybe restricting the lib folders , to only one folder would be a good idea. For example /ptokax/scripts/libs.
Putting it to PtokaX main folder would be a good idea, wouldn't it? Then we could use the method I posted above.
Yes :) it would make most sense to have them in the ptokax folder.
The thing i fear, is that plop will (:P) put em in /scripts/libs, you in /scripts, and I will put them in /
And if scripters starting to specify their own paths for it, this could be a problem when running multiply scripts from multiply authors.
QuoteOriginally posted by bluebear
Yes :) it would make most sense to have them in the ptokax folder.
The thing i fear, is that plop will (:P) put em in /scripts/libs, you in /scripts, and I will put them in /
And if scripters starting to specify their own paths for it, this could be a problem when running multiply scripts from multiply authors.
The solution is easy: write to the page that it MUST be copied to the PtokaX main folder. :D
Quotebtw. you need a ptokax version greater or equal to 0.3.3.2
Problem found...using version 0.331
Thanx
QuoteOriginally posted by bastya_elvtars
QuoteOriginally posted by bluebear
Bast, maybe it would be better if all ppls where useing the same folder for libs. Else i guess a lot of ppls will be confused about that.
Maybe restricting the lib folders , to only one folder would be a good idea. For example /ptokax/scripts/libs.
Putting it to PtokaX main folder would be a good idea, wouldn't it? Then we could use the method I posted above.
I think we should stay out of the main directory... leave that for CORE PtokaX code.
I like the idea on a \libs folder... you can still use your idea, just append \libs to the PtokaX location same as you'd append \cfg, \scripts or \texts. In fact, maybe PPK could create the \libs by default so it is ready for use....
like bluebear allready said, i suggest the folder /scripts/libs.
this so they are in there own folder (no mess).
the scripts folder may sound like a nice idea but is really bad in practice.
think of the fact that many library's use lua support scripts, ptokax would launch them when found.
the ptokax core folder shouldn't be touched.
plop
QuoteOriginally posted by HaArD
I like the idea on a \libs folder... you can still use your idea, just append \libs to the PtokaX location same as you'd append \cfg, \scripts or \texts. In fact, maybe PPK could create the \libs by default so it is ready for use....
Same here, i also think "\libs" is a good suggestion
Maybe scripts/libs would be better as we have to type less then. :D