Nightmarish Jitterbug never destorys intance...

[Peopleperson49]

This is kind of a two part post since I can't seem to find out where to submit bug reports, so if anybody can tell me where to do that it would be great. But really I suggest that somebody update the Nightmarish Jitterbug instance to destroy the script after it is beat so you don't have to wait for it to time out. On a larger server this would be important to not using up all the free instances available to players. It really also needs this check in various places throughout the script as it is very long and will keep running even if all the players quit or logout.

Peopleperson49

Modify this:

1@jtb,391,30,0	script	24 Door 1	WARPNPC,3,3,{
	end;
OnTouch_:
	if (isbegin_quest(13181) == 1)
		completequest 13181;
	warp "moc_para01",30,88;
	end;
}

To this:

1@jtb,391,30,0	script	24 Door 1	WARPNPC,3,3,{
	end;
OnTouch_:
	if (isbegin_quest(13181) == 1)
		completequest 13181;
	warp "moc_para01",30,88;
	sleep 5000;
	if(getmapusers(instance_mapname("1@jtb"))<1) { instance_destroy(); }
	end;
}

 

[crazyarashi]

I don't see the need too add instance_destroy checks. 

1 hour ago, Peopleperson49 said:

will keep running even if all the players quit or logout.

That is why we have the IdleTimeOut in the instance db.

[Peopleperson49]

I covered that above, but I guess in not enough detail. Most servers don't modify their max number of instance from 10 so on larger servers if you have several instances running somebody may hit the limit and be rejected. Assume you had a run of players doing instances and they all quit or finish them before the timer expires. Until the remainder of the time (up to an hour in most cases) nobody else can do any instances. It is as simple as doing a check to still see who is in that instance and destroy it and boom no more server resources are wasted for nothing and new instances are freed up. We optimize scripts to use less resources for the same result, so why would this be any different. This post was a result of another server having this issue so I figured I would post it here for all to see, but their are several instances that just finish out the clock for no reason. Again, this would be more for larger servers or those servers not quite paying for the fastest hardware...

Peopleperson49

Quote

On a larger server this would be important to not using up all the free instances available to players.

 

[Emistry]

what you're doing are redundant works, the instance IdleTimeOut took care of all these.

By default it has a value of 5 minutes, you should have just change the IdleTimeOut value to shorter value, like 5 seconds which you wanted.

not to mention, your approaches also end up consume more resources that it should.

beside its also the server responsibility to adjust and change the settings to fit their needs.

 

Edited September 15, 2019 by Emistry

[Peopleperson49]

I played the jitterbug on my test server and it took me about 30 minutes to beat it by myself, but it took around 20 more minutes before it finally told me that memorial dungeon had closed. This was pointed out by another server that I was working on. But five minutes isn't all that long unless you have a line of players hoping to get into an instance for some reason, lol. Anyways, thanks for the reply.

 

Also that getmapusers check only happens after a player warps out. If their are still more players on the map it does nothing. So it really uses less resources by ending an empty instance than allowing it to keep running for even 5 minutes. Also setting the IdleTimeOut to 5 seconds would use much more resources as every time the instance runs it is essentially doing the getmapusers check, well, every 5 seconds...

Peopleperson49