Hi Phil and friends...

Just had one of my - how do I do.... moments, read the manuals and delved in to examples but Im not quite there.

Im using this code for accepting the player to drop x on to a cooker (in this case) - I did plan that the ccoker will have a small but neat little puzzle for the game

The code is;

[start]drop %objn1% on cooker#room=22#objlocn1=here#objn1size<=2[acts]cmessYou place the %objn1% on cooker..#objlocn1=204#else#room=22#objlocn1=here#objn1size>2[acts]cmessThe %objn1% is too large or bulky to fit on the cooker I'm afraid![end]

No this code and the examine and get code work fine with no issues but as its a cooker I want to restrict some items and allow some (hope that garble is clear?) Ive thought about using the size and weights to do this and yes they do work but there will be items in the carrying game that are the same as the allowable obs. - e.g. I want the copper pan to go on the cooker and be used but a wooden item will burn and I dont want that to have to code against.

is there a simple add to this or do you think its beter to stear away from to much minute detail and basically force size/weights to restrict and accept that some items may be placed there with some obvious consequences?
G

Hi Gareth,

My first thought is that you could have ONLY the objects that could be allowed to be placed on the cooker all have the SAME WEIGHT....

For instance if allowable objects on the cooker all had a weight value of 2

No other objects in the game therefore could have the that value - only the set of objects that could be placed on the cooker....

And then you could do:

[start]drop %objn1% on cooker#room=22#objlocn1=here#objn1size=2[acts]cmessYou place the %objn1% on the cooker..#objlocn1=204#else#room=22#objlocn1=here#or_objn1size<2#or_objn1size>2[acts]cmessThe %objn1% is not something you would put on a cooker![end]

'========

My other suggestion is to place another entry ABOVE your original that deals with the objects that lie within the acceptable weight range but are not meant to be put on the cooker for various reasons:

[start]drop %objn1% on cooker#room=22#objlocn1=here#objn1size<=2#objn1<>x#objn1<>x#objn1<>x#objn1<>x#....etc...[acts]cmessThe %objn1% is not an appropriate object to place on the cooker, I'm afraid![end]

rem: you have several #objn1<>x# conditions..
x being the numbers of ALL the several objects which ARE allowed on the cooker

[start]drop %objn1% on cooker#room=22#objlocn1=here#objn1size<=2[acts]cmessYou place the %objn1% on cooker..#objlocn1=204#else#room=22#objlocn1=here#objn1size>2[acts]cmessThe %objn1% is too large or bulky to fit on the cooker I'm afraid![end]

However I think my first idea was probably better...?!

Phil.

HI Phil.

Yes I think Op 1 is the best as it appears to be the least labour intensive and of course less code to mistype and have to debug. Just thought Id ask incase there was a more simplisting and new way of restricting.

Thanks again

Gareth