Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!
v139 was the one PWi "opened" with right? If so that's the primary one I knew because that's where I started, and remained (even though I did roll a few toons on PW Malaysia [cubizone?])... I'd love to have played something even older though! I know I wasn't a huge fan of Genies either, and PWi "opened" with those too!
I suppose the REAL nostalgia is with 3 races/6classes NO genies, NO auto-path (whatsoever), etc!!! I remember when you didn't even have a (find) quest list! You would click to "find quest" er whatever and it would just literally give you ONE at a time; It would say something like "I hear the Elder of Ethersword is looking for you" LMAO
v139 was the one PWi "opened" with right? If so that's the primary one I knew because that's where I started, and remained (even though I did roll a few toons on PW Malaysia [cubizone?])... I'd love to have played something even older though! I know I wasn't a huge fan of Genies either, and PWi "opened" with those too!
I suppose the REAL nostalgia is with 3 races/6classes NO genies, NO auto-path (whatsoever), etc!!! I remember when you didn't even have a (find) quest list! You would click to "find quest" er whatever and it would just literally give you ONE at a time; It would say something like "I hear the Elder of Ethersword is looking for you" LMAO
I know at least one private server with all what you named (russian ThePW). You can even set up own private server with these properties (it's version 1.3.1). But isn't it boring just to kill mobs and gather resources? Cards, glyphs, reawakenings, more skills, classes, etc. were introduced to make things less routineous and more funny (we can play with it, make variants of characters). Also there are more conveniences in later versions, debug commands, functions, etc. I would dream about server files above Elysium.
Well, I have made up my mind! With the TEN year anniversary of this release right around the corner - I have decided to do an update! Honestly, I was going to do it for myself (for my archives) anyway, so why not share it right!? After all, what better way to commemorate the TENTH year anniversary than to pop it out again, and updated, and maybe a little better polished...!
Of course the ACTUAL anniversary (at least according to the first post) is ACTUALLY ~ 2 MONTHS, 2 WEEKS, and 4 DAYS away, or, 77 days away ~~ but who is counting >.>
I've also decided I'd just release it immediately seeing as things with me are always changing now... At a pretty rapid pace! Not to mention there are general "IRL" uncertainties (especially with BS like "THE BEER VIRUS" {what I'm calling "covid" for those who don't know} too)! To be completely honest, for the last 5 years ,er, however long I've been inactive... My PC has been sitting in the closet (POWERED OFF ) literally collecting dust! My server(s) have been in the attic (also powered off) literally, collecting dust... Thinking this type of scenario may arise again, I'm just going to dump this "Special Anniversary Edition" on you all now! Plus, 2020 really has sucked balls! So I had to do SOMETHING to make sure there was SOMETHING good about it (LOL)!
I have not done a whole lot with the older versions other than "fine tuned" some stuff that was driving my CDO crazy (it's like OCD except the letters are alphabetical - AS THEY SHOULD BE)! It is updated and includes 131 136 146 151 153 155 and that FW "throw in"... I also remember once upon a time I was trying to keep things within CD capacity (what a difference TEN years makes)! Now, I've kinda tossed that idea out the window, because I know people seldomly use ANY optical media any longer, CD/DVD/BRD/ETC... Everything is either straight up digital / download or "USB sticks"! So the new "Special Anniversary Edition" is just over capacity of a single layer DVD (you would need to burn it to a DL DVD if you wanted to burn it to that ancient 'optical media')... PW_DEV would fit on a single layer DVD... Everything else, thanks to the clients being STUPID BIG, well - hope you have a BRD burner... And sadly, even the WHOLE release wouldn't even fit on a DL BRD, because it exceeds 50GB... Oh well, to hell with optical media anyway!
For the most part, this is also completely NOT compatible with previous versions/releases - primarily because I've moved some of the "updates" to the BASE version (v136)... Which is also still the case... v136 is the BASE version and MUST be installed first, prior to installing any of the "addons" (131 146 151 153 155 fw)... Primary example is having the newest up to date "pwversion" service - moved to the v136 BASE... So, if you managed to install an old install of the BASE-136, and try to install the newest 155, while it should technically work - I will NOT support this, because, when you type "service pwversion" the 155 will NOT show up in the pwversion service... Because (again) that has been updated on this releases v136base!
That being said, I also don't see much reason to release the individual servers any longer, as they all ALMOST fit on a SL DVD! That being said, if you're willing to DL a CLIENT that is almost ELEVEN GB, then you should have NO problem downloading this new/up to date server PACKAGE that only weighs in at 4.73 GB! Just remember, that 4.73 GB is ALL of the server "payloads" (136, 131, 146, 151, 153, 155, & fw)!
Also, I did put PW_DEV.iso in both the "servers" and "clients" download "folders" - please note that, these are the SAME exact file... They exist merely for redundancy!
Also, yes, I chose to STICK with the old butt Ubuntu12.04.3 - there was no chance in hell I was going back to fiddle with those stupid ia32-libs to "update" the release to utilize a newer version of Linux... That being said, those who really know what they are doing anyway, will not need to ask for help "updating" their OS, or using a completely different flavor of Linux even! I chose and stuck with Ubuntu12.04.3x64 for a reason; so that I could make this package so simple you could almost literally teach a monkey how to install it! Best way for someone to learn how something works is to fiddle with something that already works IMHO... So, if you don't like using "old butt" 12.04.3, start out with that. Until you learn enough to do whatever you want to with it! For those who don't know or remember, this package could actually be installed 100% offline... And that is the key reason there are "strict" limitations (like using Ubuntu 12.04.3x64)... I went through the hassle configuring ia32-libs to be installed offline WITH the BASE (v136) package (and I remember it being a REAL Pain In The butt)! So the included ia32-libs payload will probably not work with ANY other version, than 12.04.3 Ubuntu... Personally I think the ia32-libs should just be included but then hey, I wouldn't have had that challenge... But the main goal of the package was to be 100% offline install-able... If you were say, having a traditional LAN party (with NO interwebs)... Or if the interwebs blew up, or whatever the hell stood in between you and the interwebs, I wanted a package that could basically be 100% self sufficient! Needing NO external "help" or resources... So if you find yourself on an island after an EMP, but you and your lappy were safe cuz you had it in a faraday cage/bag;;; then you will still be able to install this package!!!
Any who - enough with my ranting... Hope you all enjoy this one, it likely will be the LAST (especially if the leaks really do stop @155)!
Out of curiosity...
I have tried everything but no matter what I do. anything I download for the package is corrupt? anyone else having this issue? anyone have a reupload or a mirror on a different site?
Out of curiosity...
I have tried everything but no matter what I do. anything I download for the package is corrupt? anyone else having this issue? anyone have a reupload or a mirror on a different site?
No problem, if you're still running into issues I would take a look at possibly an error in one of the files itself.
sometimes it throws a different error however I know with my personal experiences I have run into it. both client and server logs help a bunch when narrowing it down.
usually its the gshop files
No problem, if you're still running into issues I would take a look at possibly an error in one of the files itself.
sometimes it throws a different error however I know with my personal experiences I have run into it. both client and server logs help a bunch when narrowing it down.
usually its the gshop files
You clearly didn't use the package in it's entirety either... The server and clients from this release/thread/post are all working - *together*... Not with mix and match whatever you want... That being said; of course you can "mix and match" whatever you want, if you know what you're doing... But again, if you want things to work "out of the box" you have to download EVERYTHING from this release (server AND clients)...
Alright, (for those who want to know) so the deal was that: I made a post that got deleted, and I got rather heated about it; that's why the thread was down for a while; I got into a pissing match with the [current] mods... At this point I do blame myself more than them because I was in such a state that I wasn't able to clearly communicate with them any longer (all I really could/did do was rage)! Long story short I had made a ranty (anti Win10) post, and had just recently spent ~10 hours helping someone out! So I had/was actually forgetting what I had posted that they had deleted (I have CRS ~ Can't Remember poop)! So, if they're not against it, for posterity, I will leave the ORG deleted post in a spoiler, but leave a more (proper) on-topic and hopefully less ranty post here, in it's place!
Nice! Sadly, I (still) cannot condone the usage of Win10, it is pure trash IMHO. I literally just "fixed" a laptop for a friend that was Windows 10. MicroSNOT has done everything they can to STOP you from stopping their updates. And THAT (IMHO) is shenanigans...! If it's MY machine, and MY OS, then *I* chose when and what happens, NOT you (MicroSNOT)...! My friend complained about not being able to turn off this auto updating BS so he gave it to me. I of course recommended just having me wipe it and install Win7, but for whatever reason he does need 10 (maybe for work)... So I begrudgingly agreed to attempt to find a fix, but also disclosed I may not succeed (because I HATE 10 - and know very little about it because of such)... I *THINK* I finally succeeded, by literally not only stopping the W/U "service" but by also DELETING it! I actually got so pissed I just considered it "done" and let him know I only THINK I succeeded... Because, and as I let him know, there was ANOTHER service in there called something like "windows update medic service", and I could NOT delete IT >.< There was LITERALLY nothing I could do to delete THAT service... So I warned him that I could foresee THAT service, somehow (later on) "fixing" the windows update service that I had stopped and REMOVED... But at least "for now" Windows Update was "disabled"...
Now of course if you're "geeky" enough, like myself, I could also just BLOCK all outbound communications to "MicroSNOT" in my router/gateway; this however isn't a very realistic solution for most people, like my "non-techy" friend! It's also not a long term solution since, upon changing router/gateway hardware, or switching ISP - you would need to do this (all over) again... So not a solution one could easily set up for a "non techy" friend... As soon as they changed ISPs, or changed or upgraded their router/gateway - or their ISP performed a "silent update" to the gateway, could undo this action too!
But anyway, that's the straw that broke the camels back for me, I will NEVER "upgrade" to Win10, and never use it at all if I can really help it... Windows 7 is where the train stops for me. MicroSNOT has gotten out of hand...!
I thereby do NOT support Win10 in ANY way shape or form!!! But if it works for you, well then, power to you, and I am happy for you
Basically, I do *not* recommend Win10 (and VMWare 16+) for running the server from this release. I <3 VMware but it does seem after helping multiple people that Ubuntu 12.04.3 itself doesn't want to function on VMWare 16+, only v15x or lower! So, that being said, make sure you use VMWare v15x or lower if you're going to be checking this out on a Windows host!
That being said, I also do not recommend Win10, I do personally hate it! I do recommend Win7 if you're going to be checking this out on a Windows host. That being said, I can not and do not recommend (ever) actually running a server from a Linux virtual machine within ANY windows host in the first place, not for a 'production environment' anyway! There's nothing wrong with using a Windows host and a Linux virtual machine for experimentation and learning however! Also, as a side note, just in case you couldn't tell this release is not ready "right out of the box" for a "production environment" either! The whole release is primarily meant as a means to learn enough so that you can set up a production quality server on your own Also, the client should work on Win10, at least I know the official "retail" game is still going, and since Win7 is EOL, the client surely should work on Win10! But when it comes to the server, you may desire to save yourself the headache of using a virtual machine at all in the first place, and set it up on a dedicated Linux machine!
Moving right along, one of the issues that I have seen come up almost *every* time now, when DEALING with Win10 is the AUTO UPDATE... This comes up in regard to PW, and it comes up in general too... So: if you ARE running Win10 and you need some help disabling auto update; MicroSNOT has all but removed any "native" ways of doing this (one of the reasons I will NOT switch to it - not that I cannot get around it, just as a matter of principle at this point)! So, that being said, there's not going to be any "easy" native way to "just turn it off"! Almost every method is going to be "complex" or "geeky"!
One way you could do it, would be to block the proper IP addresses (and or domain names) at your router/gateway... Simply use a program like
You must be registered to see links
(process monitor) -or-
You must be registered to see links
to establish where Windows Auto Update is connecting to, then block ALL of them! There may be pre-made lists floating around the interwebs too (just check the dates on them) I personally think this method may be the easiest, but only if you're already "super 'geeky'" when it comes to networking; if you're not I could easily see that being "too hard" or something "going wrong". That being said, if successful - you wouldn't have to do this on every machine in your network, you'd ONLY have to do it at the network level, and it would effect every machine in your network : That being said, this is not a method I would 'set up' or 'help' someone else with, because all it takes to nullify your "work" (or help) would be for your friends ISP to perform a "silent update" of the gateway/router, or if they changed the gateway/router (your friend or their ISP), or if they flat out changed ISP's! Basically, unless you're doing this on hardware that you/they completely own, it may need to be "re-done" over time (depending on your circumstances)! I cannot really post too much info/help on this as, hardware/firmware is VERY different among ISP's, countries, people, ETC! You'll just have to know what you're doing (or figure it out) on this one!
The next method actually involves REMOVING the system service "WUAUSERV" AKA "Windows Update". First you're going to need the
You must be registered to see links
. First you're going to want to stop the service (from services.msc) then use instsrv.exe (from the resource kit) to remove the service! I also recommend removing "BITS" AKA "Background Intelligent Transfer Service" since that is something else Windows Update uses (Pretty sure you'll lose MSN explorer by doing this, but who uses that anyway!?)... First "run" "services.msc" and stop the BITS and WUAUSERV services, then run a "cmd" (command prompt where instsrv.exe is) "instsrv BITS remove" and "instsrv wuauserv remove". poof no more auto update!
Now I have noticed on a 'newer' system they even actually have a service called something like "windows update medic service", and there was literally nothing I could do to get rid of it! So, if you have that, I wish the best of luck to you (as I'm guessing at some point it may be able to STILL restore your auto update stuff, minus the fact that you DELETED the service(s) used)! I guess the only steps you could further take in an attempt to assure it never "turns itself back on" would be to unregister some of the pertinent DLL's and DELETE those too! for that you're basically going to want to type "REGSVR32 /U "<dll path/name here>" " for each of the following DLL's if they exist in your system (remember to delete them first from the windows file protection cache and the %WINDIR%\ServicePackFiles\i386 folder)!
wuauhelp.chm (Windows Update AutoUpdate Help File) %WINDIR%\Help
Finally, delete the "\Program Files\WindowsUpdate" folder if it exists (Note: it is a hidden directory). This directory is used by both the Windows Update website and the Automatic Update client. Also delete any "\WUTemp" folders you might find in the root of your drives. (This folder is also hidden).
If you are slipstreaming Windows or doing a network/RIS installation of Windows (or Service Pack) you could use this little trick to disable Windows AutoUpdate during install: comment out this entry in i386\au.inf
[AU_regsvr_rule]
;11,,wuaueng.dll, 1 ; 1 means call DLLRegisterServer
; Commented out to not install autoupdate service
NOW, get this, all that garbage is for Win10 HOME... If you have Win10 PRO; you are in luck - it's actually relatively straight-forward for PRO users : Here's the "instructions" for Win10 PRO (disabling auto update):
"run" "gpedit.msc" (go to your group policy editor)
Go to "Computer Configuration" > "Administrative Templates" > "Windows Components" > "Windows Update".
Double-click "Configure Automatic Updates".
Select "Disabled" in Configured Automatic Updates on the left, and click Apply and "OK" to disable the Windows automatic update feature.
And I guess, hey, if anything ever changes in the future (like they decide to remove this ability from pro) "PRO" users will still have the above to reference later on!
Just a heads up (especially to anyone about to DL this now);
there will be (yet another) major update to this entire package ~ most likely (just in) time for the actual TEN Year Anniversary! One of the biggest things/features will be that, now that I am working on "monster spawner" and "ptemplate" "fixes", I will be going through and assuring that ALL versions gs has these "fixes", AND the new one for wallow control! Some more minor updates to PW_DEV.iso (like adding IDA 7.0 free - as one example)!!!
Stay Tuned !!!
I'll go ahead and leave the links live in case anybody REALLY wants it as it stands,,, but I warn: Since we're finally upon the actual TEN Year Anniversary, this update is gonna be a blow-out!!! I highly suggest, if you want it, and don't already have it; just wait until this update drops!