I was unaware that Ridemax was thought up by somebody else. It seemed like something that Disney would come up with honestly because most people can do without it.
The author is Mark Winters formerly of Utah and who now lives in Orlando with his family. He used to be a computer programmer for Novell in Utah and developed RideMax as a hobby which later became a full time business. He is a cool guy too. I have never met him but have had e-mail correspondence many times with him.
It's a good idea for a money maker but I think it benefits the creater more than the customer. The information is available anywhere and can be acquired easily.
If you have not used RideMax (RM) then you just do not know what you are talking about here Quest. Sorry for being blunt, and nothing personal

, but what you said here is just not true.
First, the RM people have taken time to gather wait time statistics for the various rides throughout the year. DLR has 65-70 rides. Their wait time statistics are included in the software.
Second, the RM people have taken time to gather walking time data between various rides. Maybe easier to get than wait time data, but not for someone from the UK (for example) who has never been to DLR. The RM walking time data is included in the software.
Third, the RM people have taken time to gather Fastpass (FP) data. When they run out on different days, when the return windows are, etc. The FP data is included in the software.
Fourth, the RM people know how to "tweak" data for MM days, TTMM days, Grad Night days, special event days, etc., and how to adjust their data when new wrinkles are introduced like Nemo Subs, POTC refurbs, Tom Sawyer Island refurbs, etc.
Fifth, the RM people have developed optimization algorithms to sort through the different ride combinations. As a professional myself who works in the field of numerical optimization, I know how the number of potential combinations quickly becomes astronomically large. Like trillions or quadrillions or more. The optimization algorithms are included in the software.
Where is the wait time data "available anywhere" posted or published? Where is the walking time data "available anywhere" posted or published? Where is FP collection and return window data "available anywhere" posted or published? I have looked far and wide and RideMax is the
only place I have ever seen such data made available. For WDW the Unofficial Guide folks have that data but only make it partially available.
I'd be more than happy to plan out a day for anybody wanting to go on as much as possible. I'll even do it for free.
I would issue you a challenge. Select a busy day at DL. Choose 30 rides. Then you plan out an itinerary and then let RM make their plan. Then have two people follow each plan and time how long they wait in line and how much walking they do. If you beat or do equally well as RideMax
then I will believe you - and buy you a nice dinner

. Until then, I don't believe you. And it is not because I doubt your abilities and knowledge which I am sure is vast. It is because I regularly see how optimization algorithms can outperform humans on these types of problems.
Heck last year we were working with a major oil company who had designed a pipeline using their best designers. We used optimization algorithms to show how they could combine their design elements differently and save $100 million (on a $900 million pipeline). They were floored. These were world class pipeline designers with vast experience and they overlooked $100 million in opportunity. Happens all the time. It is the exact type of thing where computers excel.