May want to get rid of, goto end, and just add in returns.

Lyndonarmitage1 wrote:

I did that and that didnt work, so I decided to do go to ends.. Still I need Help

Bad decision. Lord was right- turn all those "goto end"s into "return"s and never use goto again- it's bad practise.

The only time you should use goto is in situations where there is no other good alternative, which in thise case is clearly not one of them.

It'd be useful in future if you could actually point out the error line-
Mine Files.dm:185:error::invalid expression
In this case, the error is in Mine Files.dm, line 185. You can press ctrl + G in Dream Maker to go straight to a line.


Here's the reason your code is screwed up:



You're handling input all wrong. Input *returns* whatever the player selects from the box, right? Therefore you have to have something to catch whatever input returns back to it. Currently all you're doing is posing hte question "What would you like to do?" to the player and their choice is just thrown down the drain.



Notice how that works? The variable option equals the player's choice, so now if you want to put some if statements in you have something to actually base it on.



However I'm going to put my neck out on the line and assume the reason you made the mistake of not checking the input()'s results with a variable was because you were likening your code to code that uses a switch(). To be frank, you did it wrong ( >=| )- here's how to do it right. :)



The switch() takes whatever variable you put into it (in this case, option) and any if() statements indented after the switch() statement will automatically assume you're talking about whatever var you put into switch() - in this case, option.

Here's a bit of your code changed to start you off:



The cool think about switch() is that it only takes into account the if() statement group once (I think- anyone more experienced than me finds an error in this, please correct me)- what I mean is this:


switch_example would output "Switch example: 10" wheras normal_example would output "Normal example: 15".
In the normal_example verb it'd go through each if() statement consecutively, so you'd have to stick in loads of if() else statements to get it to work how you might want it, whereas switch() only takes into account one if() statement. Just compile the above and see for yourself.


I think you're handling your shop system wrong. Remember last time when I showed you how to improve your mining system? You should try and do it like that.



Like that. And have less if() statements- don't manually write out if("Copper"), if("Iron Bar") and so on. Make it more intelligent- use text2path and awesome use of the new proc and so on to make it automatically make whatever object you decide the shopkeeper to have.

I wrote more information about it here: ID:498177

I suggest putting in the extra time to use the way I described because it'll save you hours of work later on. Say you want to add a new type of rock to your game? You'd have to spend hours and hours going through your code adding loads of fiddly little if() statements to accomadate the new rock type. With the system I am suggesting, all you'd need to do is change one or two variables and volia, it works!

Last little bit- notice the:

bits? More specifically, the null|anything stuff? It adds an extra "cancel" button to the input(). Make sure that you have some way of recongnising it though- after the input put a if(!option) or some such then you can return the proc and stop it running if the player chose the cancel option.

Thanks Hiead and Tiberath!

Thank yuo I was unaware of the importance of switch().
This has really helped!
Honestly with this knowlage i can master the input proc.
Thanks Hiead and Tiberath!