Object type in feeding filter (CSBwin)
Forum rules
Please read the Forum rules and policies before posting.
Please read the Forum rules and policies before posting.
Object type in feeding filter (CSBwin)
What is the fourth 'object type' byte in the feeding filter? It doesn't seem to correspond to a normal 80000 potion number when i was drinking a VI potion - it said 162
Last edited by beowuuf on Sun Apr 16, 2006 6:50 pm, edited 1 time in total.
Then it's coming up wrong I think
A healing potion, type 85300 something or whatever was being listed as 162 by the feeding filter - so either I did something wrong or it did!
I was also trying to be sneaky and pass a message to the filter that would ape a feedign event - didn't work, but should it?
A healing potion, type 85300 something or whatever was being listed as 162 by the feeding filter - so either I did something wrong or it did!
I was also trying to be sneaky and pass a message to the filter that would ape a feedign event - didn't work, but should it?
-
Paul Stevens
- CSBwin Guru
- Posts: 4318
- Joined: Sun Apr 08, 2001 6:00 pm
- Location: Madison, Wisconsin, USA
162 is a VI POTION
The Feeding Filter documentation points to a
list of object type definitions.
feeding event? That's silly. The filter modifies the
parameters during a feeding event. Modifying the parameters
when no event is active is like talking into the telephone when
nobody is at the other end. There ain't nothing to filter and
nobody is listening! A filter is like this:
Your friend arrives at the pizza parlor and calls to ask what
kind of pizza to bring. You answer the phone and say that
you want pepperoni. So he buys pepperoni. If you lift
the receiver at a random time and say 'pepperoni' it is not
likely to be satisfying to your appetite.
The Feeding Filter documentation points to a
list of object type definitions.
Are you are trying to call the filter from other than aI was also trying to be sneaky and pass a message to the filter
feeding event? That's silly. The filter modifies the
parameters during a feeding event. Modifying the parameters
when no event is active is like talking into the telephone when
nobody is at the other end. There ain't nothing to filter and
nobody is listening! A filter is like this:
Your friend arrives at the pizza parlor and calls to ask what
kind of pizza to bring. You answer the phone and say that
you want pepperoni. So he buys pepperoni. If you lift
the receiver at a random time and say 'pepperoni' it is not
likely to be satisfying to your appetite.
Actually, I made some attempts to check it and if it didn't satisfy my appetite, it did raise the appetite of curiosity of my girlfriend. Just before she became scared and slowly stepped back to the nearest exit, that is. Gazing at her, I said one more time "pepperoni" and laughed hysterically. I felt very fulfilled after that.Paul Stevens wrote:If you lift
the receiver at a random time and say 'pepperoni' it is not
likely to be satisfying to your appetite.
Hmm, I'm working from an offline version of the documentation saved, but there was no link to the object list so it made it sound like it was the normal one
And the reason I tried it with the feedign filter was the documentation made it sound like when feeding event happened, it took the parameters, then blocked the feeding action, and initiated the feeding through a call from the filter. I understand that all other filters work by interrupting the function call, playing aroudn with the parameters, then lettign the fucntion get back on with its job with those new parameters. I though the feeding filter was wackily different and actually initiated a call using the parameters it stole from the original event.
I too like to pick up phones and say'pepperoni' - because there is always the chance someone just rung up just that very second - and hey, maybe those double glazing people want to make a sale and will get me a pizza!
And the reason I tried it with the feedign filter was the documentation made it sound like when feeding event happened, it took the parameters, then blocked the feeding action, and initiated the feeding through a call from the filter. I understand that all other filters work by interrupting the function call, playing aroudn with the parameters, then lettign the fucntion get back on with its job with those new parameters. I though the feeding filter was wackily different and actually initiated a call using the parameters it stole from the original event.
I too like to pick up phones and say'pepperoni' - because there is always the chance someone just rung up just that very second - and hey, maybe those double glazing people want to make a sale and will get me a pizza!
