For the Script class.

Log the message to the console when this is called and then stop the script.

Useful for, for example:

 

if(outofsupplies) stop("Out of supplies");

else if(!coolenough) stop("Not cool enough");

else if(!canbank) stop("Couldn't find bank");

 

Also: stop (String message, boolean logout) because why not.

 

Cheers!

 

It's also a 5 second job for any scripter to write this himself, but I still think this would be a usefull addition to the API.

       public void stop(String message) {
		log(message);
		stop();
	}
	
	public void stop(String message, boolean logout) {
		log(message);
		stop(logout);
	}

Edited April 22, 201511 yr by Botre

You can just add a log before you call stop.

I don't see alot of benefit from this Personally.

You can just add a log before you call stop.

I don't see alot of benefit from this Personally.

 

Verbosity is the main reason I suppose

 

if(outofsupplies) getScript().stop("Out of supplies");

else if(!coolenough) getScript().stop("Not cool enough");

else if(!canbank) getScript().stop("Couldn't find bank");

 

vs:

 

if(outofsupplies) {

getScript().log("Out of supplies");

getScript().stop();

}

else if(!coolenough) {

getScript().log("Not cool enough");

getScript().stop();

}

else if(!canbank) {

getScript().log("Couldn't find bank");

getScript().stop();

}

 

3 lines vs 12 lines, which one would you rather write ? :x

Edited April 22, 201511 yr by Botre

Verbosity is the main reason I suppose

 

if(outofsupplies) getScript().stop("Out of supplies");

else if(!coolenough) getScript().stop("Not cool enough");

else if(!canbank) getScript().stop("Couldn't find bank");

 

vs:

 

if(outofsupplies) {

getScript().log("Out of supplies");

getScript().stop();

}

else if(!coolenough) {

getScript().log("Not cool enough");

getScript().stop();

}

else if(!canbank) {

getScript().log("Couldn't find bank");

getScript().stop();

}

 

3 lines vs 12 lines, which one would you rather write ? :x

 

Any scripter can write it himself. I don't see the point in adding this to the API.

I don't think that we should flood the API with useless functions that we don't need.

Edited April 22, 201511 yr by Xerion

I see what you are saying, but since the api has 2 stop methods then they would also need 2 methods that take string parameters. So alek would have to add 2 methods to keep ot consistent.

Stop (boolean, string)

Stop (string)

Or something like that. Just seems a bit unnecessary imo.

Still love u thou

I see what you are saying, but since the api has 2 stop methods then they would also need 2 methods that take string parameters. So alek would have to add 2 methods to keep ot consistent.

Stop (boolean, string)

Stop (string)

Or something like that. Just seems a bit unnecessary imo.

Still love u thou

 

Nah main fair enough :p

Just figured I suggest it since I needed it myself a while back and perhaps some others were interested in it ^^

Nah main fair enough :p

Just figured I suggest it since I needed it myself a while back and perhaps some others were interested in it ^^

I'm just playing the role of alek.

I'm pretty sure that is what he will think if I had to guess.

:alek: d

Edited April 22, 201511 yr by Mysteryy