PW does not use AND luas it's in npcgen they're disabled
- - - Updated - - -
PW does not use AND luas it's in npcgen they're disabled
Better to just NOT recommend ANYTHING that will confuse new-comers !
That being said:
Don't use anything other than bridged (+ replicate physical connection)
*solved*
Those NPC exist on element.data, however they dont show up on npcgen.data
I believe this could be fixed just creating a new forge and linking to their ID.
But this will not solve entirely the problem, since the Lunar & Warsong npcs to spawn vile is still missing.
Without vile bosses we cant get mold or badges to craft anything on those forges, unless we created those npcs manually but this should be also checked in tasks.![]()
Last edited by SrlyBeeto; 17-05-21 at 09:15 PM. Reason: Warsong doesnt have npc for vile also
i mean simple fix would be to add those npcs into npcgen.data... as for the bosses you'd need to load up the npcgen for the cave and make sure they are in there along with the trigger and or quest to spawn them.
If I remember right that is. someone feel free to correct me.
That instance hasn't changed since 1.4.7 I think..? you can use older npcgens on those instances and see if that works. IF It does NOT, then the problem lies in aipolicy, NOT npcgen. (also I believe tasks can spawn NPCs not on a map, since we can do it with debug commands as well
There is a new PW_DEV.iso available... New PW_DEV checksum is:
File: PW_DEV.iso
CRC-32: 556c7dc6
MD5: 9ee57991e75982c1d5ff3e2fc6018b60
SHA-1: 7667bbe5d66b24c7a24ee7de8d219ff421b3dffe
SHA-256: 4307903059ca99d1375eb2f51042c4d8d6ea628fb2fa34b0d15b2f64c798b4dd
SHA-512: 945c7b2285a722937e942ddf5103a3ab2557448525c7df68550834fd49bd6a3f419efc0626138d7c0d19756565738f8e6d8eedcae1931dfd97bbbeede3aea133
SHA3-256: 20a1a85078c524c5b61643d74d3a6cc40d87275b9ad624177a276ccfd6794ce1
SHA3-512: 16c7f9d1eda51f369e78fa506c62fc46e94b04b02c22ebc6707ac49d2085a3801fce7ccecd99781177a0ded0908abaa48f30bcff3e8678c236b939d26559ac13
great release been following the release since ubuntu 10 pw1.3.6.
if i remember you had a previous release that we had to download the 136 and 151 installer packages individually (on ubuntu 12.04.3 sometime in 2014), on that release pwadmin can stop the whole server and start and stop the maps individually making the server run on machines with low ram, allowing local play to just start the map as needed and stop when map is empty (if no players on the specific map )
i was wondering for the SAE march 2021CRC-32: de4fce2arelease,
server runs all good as expected but stopping the whole server via pwadmin would leave the authd server running not allowing the server to start again via pwadmin, same goes with maps once started pwadmin won't allow you to stop maps individually creating the need for the whole ubuntu server to be rebooted just to stop authd (if terminal commands not used ie: kill or pkill)
has anyone figured this out yet, this was asked already i think if so i apologize
server running on a vmware workstation version 15.5 2 cpus 8-10 gb ram setting on win 10 20h1 (even the ubuntu 10 version runs)
server tests done on vmware 9 running on win 7sp1 and windows 10 2004 (ignoring windows 10 error message for vmware)
i used to run it on an old physical machine 8 gb ram but doing maintenance on it
thanks in advance
** im trying to teach my 9 yr old daughter linux and server side things and trying this out to get her interested
also, so she could play pw on her own, start the server and stop the server without going into the terminal side of things ... yet
edit :
looking into the pwadmin serverctrl.jsp old release vs new some parts of the new release have been commented ( // ) line 44 to line 53 was this intentional?
Last edited by arawsg; 21-05-21 at 09:39 PM. Reason: added info
I honestly would not have known because I hardly if ever actually use pwAdmin (at least not to start/stop server/maps anyway)... I almost always do that manually, or by script...
Not sure what comments you're referring to, I haven't commented anything out, at least not recently - if my memory serves me correct...
But at first glance I have NO problem replicating it; after starting the server using pwAdmin - it says authd is "offline" (even though it's not)... Which I'm guessing could also (strongly) have something to do with it not stopping it... ... ...
Things are picking up for me in other areas of life again though so I'm not too sure when I'll actually be able to investigate or even "fix" anything... =\
Uhg, and that would mean yet another server ISO update @.@
yep, doing it manually works.
Trying to look into it further, i took off the // on specific lines in pwadmin serverctrl.jsp replicating an early release still did nothing for authd stopping via pwadmin , im going to keep on looking into it
but yeah thanks and no hurries
attend to life and best of luck![]()
You could always write your own script and have pwAdmin call it instead of whatever it does .. ?? .. ??
- - - Updated - - -
Well thank you for invoking/inducing my insomnia (no JK it's really not your fault) but, I went to do a lil testing and even 136 isn't working for me RN
So, knowing full well that too once worked, I wonder if it isn't something (somehow) related to newer version of Ubuntu? That doesn't even make sense even to myself RN but then again I am sleep deprived at this point >.>
- - - Updated - - -
well in the meantime, for manual or scripting use you could use something like the following to stop authd:
kill -9 $(ps aux | grep "./authd" | grep -v grep | awk '{print $2}')
same exact thing/concept for maps
kill -9 $(ps aux | grep "./gs is02" | grep -v grep | awk '{print $2}')
where obviously is02 equals the instance you want stopped
- - - Updated - - -
That's how I "manually" stop stuff
- - - Updated - - -
You could get even a little fancier and "borrow" this, this is a small script I just tossed together that literally stops either ALL maps, OR any single specified map (one at a time):
- - - Updated - - -Code:#!/bin/sh case "$1" in *s**) kill -9 $(ps aux | grep -v grep | grep "[.]/gs $1" | awk '{print $2}') ;; *) clear echo "" echo "Would you like to stop ALL maps?" echo "y/N" echo "" read -s -n 1 confirmall case $confirmall in n|N) clear echo "" echo "NO maps were stopped..!" echo "" ;; y|Y) kill -9 $(ps aux | grep -v grep | grep "[.]/gs $1" | awk '{print $2}') clear echo "" echo "ALL maps have been stopped..!" echo "" exit 1 esac exit 0 exit 1 esac exit 0
Oh and I even threw in the "failsafe"
that is, it "checks" if you actually WANNA stop ALL maps if you just run the script with no "command line arguments"... Then you have to hit either Y or N to stop ALL
otherwise you could run like ./script is02
and it would stop ONLY is02
- - - Updated - - -
also, more specifically to you, I know you may be skeptical of getting her on a terminal already, and I would agree with probably not trying to overload her with having to actually manually do so much (ps aux grep kill pkill n all this shit may be a bit of an overload)... But I would think if you tossed that script together, that could be a great way to start learning terminal; by running scripts you've made (or borrowed)...
Then you know that's going to lead to "how to make scripts"!
But yea, kids minds are sponges - the earlier the better!!!
But I would think that may work out for you two as well, just tell her "ok, if you want/need to stop a map you type './stopmap is##' to stop that map"(and ofc there's nothing wrong with using pwAdmin to get the numbers/list!) And like I said ./script (presumably something like stopmap or stopmap.sh [I'd personally actually just go with stopmap]) ran without something like <script> is02 - will presume to kill all maps, BUT ask/confirm FIRST!
LMK
I would also think, you could even modify pwAdmin to "call" this instead of whatever method it is currently using !
- - - Updated - - -
at this point I am trying to think about if/how I'm going to handle this for the release because, this could be ALL versions, and rebuilding ALL versions is going to give me a migraine - IF I even actually get the time to do it any time soon
- - - Updated - - -
Oh and just in case you didn't know, you could also put a script like that in /usr/local/bin
Then you can skip the preceding ./ when launching it, AND it can be run from anywhere (while in any directory)...!