Temtem Dev Tracker

I'm taking this one guess as it was the second oldest! But unfortunately there's no N!

Yes! It totally was!

Hey Tamers!

Patch 1.4 has been sent for review by the platform holders. They'll now test it and either send it back to us for fixing, or give us the green light so we can launch as planned. Remember that the estimated date of launch for 1.4 is June 19th!

I'm currently writing a post overseeing the features and changes that come with this update, stay tuned for it!

Great guess!

😞🤘

Hello!

The theme has been guessed!

The name of the upcoming Season is... Splash Up!

Here's a sneak peek, more to come as the date grows closer!

I see jaws...

The Royal Waspeen dress is to die forrrrrrrrrrr I love it

babies....... <3

This was very refreshing to read, thanks for going into all that detail and being so empathetic!

From reading your posts and others' I realize there's not really a consensus on whether to shut down ideas or not, though haha I'm unsure of whether I should really ease on the shutdowns or not, but I'll do my best to reply to the things I like or find neat.

I always feel whiny when I bring up the "I'm a whole person" argument, although it's true, but if I'm being honest reading all that negativity about you or your colleagues can really bring one down. I wish people would remember that even if I don't say so.

I love the idea of having everyone take part in the challenges, and I'll let them know!
And we have a contest in the works rn :)) I hope to be able to post it this week. I like contests too :))

It has always been my goal to create safe and open spaces, but it's definitely been a hard balance to maintain these days.

Thanks for all your o...

The issue with Temtem from the beginning was what you just mentioned, that our expectations and the players misaligned along the way. Temtem is not meant to be an MMO like WoW, Tera or FFXIV. For a team like us, that'd be delusions of grandeur, and we consider Temtem to be a miracle with the resources and experience we had. We've also very often encouraged people who only want to play the campaign and then drop off. It was first mentioned in our Kickstarter's FAQ.

So I agree with you on that point, but I also think knowing one team's limits and having a sensible vision is a good thing for devs. I understand why players are ambitious, we are always after that perfect game, but imposing one's expectations on someone else's game will always end up in bitterness and frustration. How would you propose we close that gap in ambition without changing our idea for the game, or our budget, time, resources and teams, and without antagonizing the community?

I understand why you...

Hi! Sorry about the delay, got busier. I like the first idea, but as I said in some other post, it's not my time alone to compromise so I can't say if it'll happen. Feedback ends up having to go through many teams to see if it's doable.

As for devlogs, I really like the idea, but I know in practice some of them would be very boring, like "we're still developing the 3rd Mythical, we're still working on a secret feature that we want to keep a secret from you until release". The old roadmaps still work in terms of features, and with Seasons there's a lot more info on dates, themes, and all that. I'm also, personally, worried about spoiling too much about upcoming features before the right time. I've seen it happen and didn't like the result.
But the one, true, actual issue I see with this is that I fear the community won't feel heard unless their feedback has been implemented, not acknowledged or discarded.

Hmm I think flat-out saying we haven't said a word on the subject is unfair, and the kind of argument that only cause damage and disconnection from the community. We've (I've) said in multiple occasions that the team is aware and considering the need, but until a decision has been made and it's ready to be publicly shared, we cannot give a yes or a no. When I asked you before, you said our reply should be more balanced towards doing it in the future or not doing it, but at the time of gathering the feedback no one can tell me that. That comes much later, that internal definition.

DRG has an open development-type of approach, and we had that too during Early Access, but like we've said in the past, the current stage is a bit different. I stay in contact with the community daily, but I don't have feedback approval or public news daily. I liked your idea of setting aside a couple hours, but even if the design team says yes, the coding team and art team have to say yes too, and...

Congrats!!

TRUST

Hello! I know many devs have that attitude towards feedback, and even in Crema, there's peeps who think like that too, but in this particular case and platform we were also hoping to get more insight on feedback that we might not understand where it's coming from (like in the case of the battle camera, as people who don't suffer from dizziness, or in the case of colorblind improvements). We were also hoping to stray a bit from feedback that's just an emotional feeling. Since there's many different players in Temtem, we want to know more about their needs and expectations, beyond only their feelings towards a thing.

We usually draw the line at people explaining how to code something, or why something is easy or hard to do. That's where we consider we're more qualified to make a decision, but knowing the hoped-for outcome people have in mind generally helps and doesn't harm the process.

My absolute favorite of all you've done so far, I'm a sucker for traditional oriental clothing <3

No probs! I'd love to get your opinion on the two issues/challenges I see to this.

One, I'm not in charge of design, so me reading something doesn't necessarily mean it's reached the right ears. If I, the one who can probable see most of the feedback posts, read it, but no one on the design team does, it's fallen on the wrong hands. I can forward all of them to the design team but there's no guarantee they'll have the time to read it all. I'm afraid we might be giving the community false hope.

Two, don't you think that if we acknowledge all the feedback there'll be a growing expectation that can transform into bitterness when said feedback takes too long to be implemented, or never gets implemented? Managing expectations around feedback has proven to be one of the most difficult bits around here.

What do you think, how would you work around those two things?

No, it was fine! And thanks for saying that :)
I understand and recognize the pattern you mention, and it happens around here the most, which is totally causing a cycle. It was, however, never my intention to not let people share their frustrations, ideas or feedback; when I step in on those it's usually only to correct misinformation. I have, on occasion, stopped an idea because it was impossible to add to the game and the community was placing too much hope on it. I considered it'd be best to know the truth than harvest hope for naught. But I generally see no problem with people sharing ideas or feedback as long as it's done constructively and healthily. I read, and usually don't comment on them.

I struggle with balancing expectations, and worry that if I open a door such as "what would you like to see?" knowing the Crema team's current situation, I might create false hope or cause bitterness if that only ends up staying here, as ideas and feedback. What is your pov ...

hello! I'm head of said department and I wanted to get some clarification on what you mean about saying the same thing for years? And how would you suggest I address stuff for which there's still not a solution planned (and might never be)? I don't always have an answer to stuff (sometimes there's no answer yet), and I'd love to pick the playerbase's heads on how they'd want me to communicate that to them.