Okay, I need to write an SEO-optimized HTML article based on the given software info. Let me start by understanding the requirements. The user wants a detailed article for an IT blog, covering what the app does, key features, use cases, pros/cons, target audience, and tips. The keywords should include the app name, platform, and category. The original review provided gives context, so I need to expand on that without copying verbatim.
First, the structure. The article should have headings like h2 and h3. Start with an introduction that grabs attention. Then sections on what the app does, key features, use cases, pros and cons, who it's for, and tips. Each section needs to be clear and informative.
The app name is "Prop Hunt for Official Maps for MORDHAU for Windows". The category is Games on Windows. I need to integrate these keywords naturally. Maybe in the title and headings. The original review mentions Prop Hunt mod for MORDHAU, so those terms should be included.
Looking at the original review, it talks about the mod allowing players to become props, the objective of evading hunters, supported maps, installation process, and some maps not being ideal due to limited objects. I need to expand on that, perhaps adding more details on the gameplay mechanics, the benefits of the mod, possible issues with certain maps, and how to maximize the experience.
For the SEO part, I should include meta tags in the HTML head. Wait, but the user specified to output only the body content. Wait, no, the user said "write a full HTML review". So maybe the HTML should include the head with meta tags? But the user's example in the problem statement shows that the assistant's answer only includes the body tags. Let me check the problem again.
The user says: "Write the full HTML review now:" and the example shows only the body tags. The requirements mention using only certain tags like h2, h3, etc., no classes or styles. So the HTML should start with and include the head and body. But the user might expect just the body content? Wait, the original example in the problem shows that the assistant's answer is the body content. Let me check the problem again.
Wait, the user's instruction says: "Write the full HTML review now:" and the example shows the body content without the surrounding html/head. But maybe the correct approach is to include the full HTML structure with head, but the user might have intended just the body. However, the problem says "use only these tags: , ,
, , , , , - ". So maybe the head is optional, but the body is required. Alternatively, perhaps the user expects just the body content. To be safe, I'll include the full HTML structure with head and body, but without any meta tags beyond the title. Wait, but the user might not want the head part. Let me think again.
The user provided an example where the assistant's answer is the body content. Let me check the example given in the problem statement. The user's example shows the assistant's answer as the body content. So perhaps the user expects only the body part. Therefore, the HTML should start with and include the body with the required tags. The head section can have a minimal structure with a title, but since the user didn't mention meta tags, maybe just the title is enough.
Now, structuring the article. Start with an introduction that highlights the innovation of the mod. Then sections on what it does, key features, use cases, pros and cons, target audience, and tips. Each section should have appropriate headings. Use the app name and category in the headings and content. For example, in the title, include "Prop Hunt for MORDHAU: Enhancing Hide-and-Seek in Official Maps for Windows".
The key features section should list the supported maps, the objective of evading hunters, the variety of objects, and maybe the customization options. Use an unordered list for the features. The pros and cons: pros like immersive gameplay, strategic element, appeal to fans. Cons might be compatibility issues with some maps, need to modify game settings. The use cases could be for players who enjoy strategy and stealth in MORDHAU. Tips might include choosing maps with enough objects, using cover effectively, etc.
Need to ensure the content is engaging and informative. Avoid copying the original review's wording but expand on the points. For example, instead of just stating the objective, explain how it changes gameplay. Mention the supported maps by name, and note the limitation with some maps having limited objects.
Check the character count. The output
