Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It just means he pushed back the next map so he can make the game more stable. Which is a good thing.
The game would die if it was an unplayable mess, regardless of how many maps it had.
This.
A shift in priorities does not mean an abandonment of updates. Calm yourself. If you're bored, take a break or add a spin on how you play with your friends. Go in with roles to act out or make silly stipulations like "Candle only" runs or stuff like that.. Or just..Keep enjoying the game and...Wait for updates.
kinda not how game develope goes tbh you add content then fix as why fix when that new content can break everything youve just sat and fixed
Plus, adding a MAP does not usually cause bugs in AI code, game loading, or object usage to reappear. Meaning he can bugfix before making a new map.
And it's up to the dev to do it however they want. There's no rules to game development. If he wants to focus on making the game more bug-free before he makes a new map; he's fully allowed too.
There is a difference between bugs in the game's core mechanics and map specific bugs. Why triple* their workload when they can just focus on fixing the bugs that exist now, improve stability and consistency and then move on?
(*Triple as in, bug fixing, map developing and bug testing for the new map.)
Why do people think they know more than the dev about what to do?
If he wants to make the game more bug free, then add a new map (which, to my knowledge of coding, should not suddenly make the game less stable or break items); then it's what he's going to do.
Edit: Plus, if he decided to add a new map while the game was buggy, people would whine he does not have his priorities straight.
In larger teams, bug fixing and content often run alongside each other, unless theres something critical.
In smaller teams they have to pick and choose what they're gonna work on, and bugfixing before adding new content makes perfect sense, as then it becomes much easier to track down and fix new bugs if you know if comes from your new content over not knowing whether its the new content or the base game thats the source of the issue. It's not the only way of doing things but it makes sense. Infact often you'll see a cycle of bugfix, content, bugfix, content.
Just because you can play it smoothly without problems doesn't mean it isn't riddled with bugs that are causing problems for other folks. [/quote]
There's content and he's fixing it. Thanks for agreeing.