Either you could make them all be a subclass of one class or you'll have to put this line of code multiple times once for each class. I don't think there is a way of writing multiple classes as one.

There are methods in my XWorld XActor Classes scenario in the XActor class that allow multiple classes for collision checking.

Using Dan's classes is good, but you should look at how it is done. The interface tagging post above is a common practice and worth knowing even if you chose not to use it. Its a common design pattern called Marker/Tagging Interface Pattern. ( see also: https://en.wikipedia.org/wiki/Marker_interface_pattern )

That's the same as setActOrder(java.lang.Class... classes) and setPaintOrder(java.lang.Class... classes), but this won't help in this discussion since this is for creating a method, what timothytitus want(s)/(ed) to do (is)/(was) have an isTouching method with multiple classes. But I guess you technically can do it like this:

For 'isTouching', you could easily enough just do this: The difference is the 'isTouching' method returns a boolean value. The purpose of using multiple class arguments in those methods in my XActor and XWorld classes is to compile a single complete List object of all the various objects returned by the various classes.

We are having this discussion in a discussion of a specific topic. Read the first/main/original post/question. So my method let's him be able to put in multiple classes for the parameter (so to have the whole method is more code, but calling it like: is better than all those '|| isTouching(').

You are assuming that the number of intersectors and their types are not important -- that as long as one is touching, then the check is satisfied. That, however, was not specified and may not be the case. In fact, I doubt this thread would have even been started if it were the case, as easy as it is to write it "long-hand". True, it may have; but, then again, was not specified. I will no more discuss this unless further input from timothytitus is given, if it is given.

All of it is right there, and shows that is the case. The thread is right here, and I thinks it makes sense to be. I agree '||' can just be used but it could be that wasn't timothytitus's train of thought. The train of thought was probably that collision detection for multiple classes is needed, and there is no method for that. I'm not forcing you to reply, but the question makes sense and has been answered.