Hello Wild Ones!
We recently gathered a massive amount of feedback and suggestions regarding the new version of Wild Assault from the community. The development team has immediately held internal discussions addressing your top concerns, such as the update frequency for new heroes, PVE gameplay, and balance issues.
In this issue of the Wild Assault Dev Log, we will provide concentrated answers and updates on the core issues you care about most.
📅 Part 1. Future Roadmap
Q: What is the plan for future season updates? What is the production capacity for new characters?
A: Regarding the release of new characters, our current plan is tentatively set at 2 new Valiants per year
This decision is primarily to ensure quality. As skill designs become increasingly complex, we need more time to polish the playability of the mechanics. At the same time, we confirm that we will continue to stick to the "Small-Scale Test Server" model to allow you to participate in validation ahead of time.
Q: The PVE mode is in high demand. When will it be served up?
A: Good news! The design work for PVE is in full swing! We have already established some core directions and are currently discussing further details. Please wait patiently.
Q: Are there plans to open a Workshop or Custom Maps?
A: We are currently researching the workflow for building a Workshop. Although there are quite a few technical hurdles to overcome, increasing player freedom is a direction we are very interested in.
⚖️ Part 2. Fearless (Valiant) Balance Adjustments
Q: Are there rework plans for the two controversial Valiants, "AKAIHIME (Fox)" and "JACK (Wolf)"?
A:
Regarding AKAIHIME (Fox): We see the current controversy clearly. We need to analyze the data carefully and will consider adjustments to skills in the future.
Regarding JACK (Wolf): We have recorded the controversy surrounding the "Wallhack/X-Ray" ability (and the issue of his skill floor being too low). We are not ruling out future adjustments to his skill mechanics to provide a better counter-play experience.
Q: The roles of CROCK (Crocodile) and ULY (Meerkat) feel a bit vague. Will they be adjusted?
A:
CROCK (Crocodile): His role is clearly a "Recon." We recently nerfed the damage of his Q while expanding its reconnaissance range. The speed boost on his Ultimate is designed primarily to improve his fault tolerance.
ULY (Meerkat): He is a "Specialist" character who relies on teamwork. We are aware of the current pain points regarding his power level and are evaluating optimizations for his talents and skills.
Q: The Talent System is too simple. Will there be deeper gameplay branches?
A: That is exactly what we want to do! Currently, talents are mainly positioned to increase stats/effects. We are researching "Talent Tree Improvements" and "In-Match Upgrades," hoping to let talents truly change skill forms and bring more build variety.
🔫 Part 3. Combat & Gunplay Experience
Q: Many players report slow bullet speed and weird sniper handling. Are there optimization plans?
A: Our weapon designers are conducting a comprehensive analysis of weapon handling.
Regarding Bullet Speed: The current version is live, and large-scale changes require assessing the adaptability of different player groups. We will conduct testing and adjustments gradually (yesterday, we buffed the bullet speed for some Rifles and SMGs).
Regarding Snipers: Whether the feedback is "Overpowered" or "Feels like a useless stick," we have received these polarized opinions. We will make targeted adjustments after evaluation.
Q: There are keybinding conflicts (e.g., the F key is used for both reviving and ammo crates). Will this be optimized?
A: We are sorting out the conflicting keybinds and referencing solutions from other mature FPS titles. We aim to solve this operational pain point as soon as possible.
Q: Dynamic AI (Bots) are sometimes too strong, sometimes too weak, and throw smoke grenades that block vision randomly?
A: Our programmers are working hard to "train" them! We will continue to optimize BOT logic to solve issues like bots not entering objectives, spamming skills randomly, and inconsistent difficulty. We aim to make them smarter and more reasonable.
⚙️ Part 4. System Optimization & Anti-Cheat
Q: When will game performance issues (frame drops/slow startup) be solved?
A: The high performance cost is mainly because we put a lot of effort into "Fur Rendering." The engine team wizards are digging deep into the potential of UE5, striving to reduce resource usage while maintaining the quality of the fur effects.
Q: Is the current anti-cheat mechanism sufficient?
A: Please rest assured. We currently have BattlEye (Little Blue Bear) support, combined with an auto-kick function. This is a relatively mature mechanism. We will continue to iterate in the future to strive for a fair competitive environment for everyone.
Q: Can matchmaking be optimized? We often encounter uneven team numbers.
A: This is a "long-standing" issue, mainly limited by the current size of the real-player pool. Sometimes uneven teams (like 2v8) appear because some players fail to enter the battlefield after assignment. We are thinking of ways to optimize the matchmaking logic and doing our best to ensure match fairness.
Closing Words: As we said in our answers, "The general direction remains unchanged, and we will persist."
Thank you all for your tolerance and support of Wild Assault. Although our team size is limited, our steps toward optimization will not stop. Please look forward to our future updates!
That’s all for this week’s Wild Assault Dev Log. See you next week! If you have questions regarding other aspects or detailed inquiries about the directions above, feel free to leave a comment and give us feedback anytime！
Combat Cat Studio
X：https://x.com/WildAssaultGame
Discord：https://discord.gg/WildAssault