Diese Rezension ist noch nicht übersetzt — wir zeigen das Original (English).
Larry Laffer looked around the world and decided Miami was boring. No way, he wants to cruise through the Caribbean, Mexico, and Polynesia searching for the woman who'll be worth every trip. The result? The second Leisure Suit Larry from 1988 is exactly the mess you'd expect — packed with cheap gags, double entendres, and exotic settings that play it surface-level without any deeper entertainment value.

It's a point-and-click adventure where you need to click on everything possible to get Larry shuffling from one location to another. Story? Meaningless. Goal? Rack up points, flirt with girls through simple word games, and collect random, barely relevant items. The graphics are pixelated, colors bounce between neon red and washed-out blue on your monitor, and the music quirks along with synth sounds you'll remember for a long time — not necessarily pleasantly.
Playing it makes you want to groan. The game tries hard to be funny, but humor based on sexual innuendo and stereotypes wears thin fast. Fair warning: dialogue drags on, and when something sticks, you'll get bombarded with the same one-liners over and over. Controls work — click, wait, solve simple puzzles — but the pacing feels forced. You're waiting for a response that arrives at the speed of a dead phone line.
Leisure Suit Larry 2 had the guts to stay true to its original vision: be bold, be raw, don't apologize. That's respectable. But boldness without wit is just provocation, and that's exactly what you get here. Looking at it now, you see how important this series was for nineties PC gaming — the freedom, the lack of censorship — but playing it today isn't much of an experience.
If you're curious what computer humor looked like in the late eighties and you're not put off by jokes built on sex and nonsense, you can fire up Larry in DOSBox or an online emulator. It's a snapshot of an era you won't see anywhere else — purely historical evidence of how raw and unfiltered PC games could be in one package. Otherwise, there's no real reason to bother.