devtrackers.gg
This is the funniest occurrence of this bug I’ve seen, how the hell did you manage to have that many 🤣
This is the funniest occurrence of this bug I’ve seen, how the hell did you manage to have that many 🤣
Happy Holidays, dear Tamers! Hope you get some well-earned rest and some cozy fun during this season! We want to thank you for all your love and support this past year, and so we're sending you a little gift! 'Tis the season! 💝
You can redeem the code from the Redeem option in the home lobby. For anyone using a screen reader, the code reads 2022-XMAS-G1FT-YAYY
Code can only be redeemed once per account, and it will be redeemable from today until January 7th. Hope you enjoy it! 💕
We're also taking this chance to remind you that the team is on break for the holidays, and the turnaround time for some processes might be longer than usual. We apologize for any inconvenience t...
Read more External link →I acknowledge that. I'm willing to be patient. However every time I've asked on the Discord for an opt-out feature the answer was never a yes or we need time. It was just flat out, no.
So, will an opt-out function be coming when the patch hits?
I'm afraid I don't have the answer you're looking for. We're not considering an opt-out option for the time being. We'd rather work on them and make them a feature people can enjoy and like before we get to the point of considering disabling them or opt-out option which is similar to disabling them.
Let's see how that goes first. If after the changes to them you still don't like them please make a feedback post on the forums and I'll make sure it reaches the team (if it's not destructive).
I mean even if they're insistent on keeping it in the game and forcing it on us, give us an option to disable it UNTIL it's fixed. Let us disable it for now while it's atrocious, then work on it, ask us to test it again and give feedback once it's improved, and when most of the complaints are addressed yoink the ability to disable it again.
Like you don't even have to just "Yes/No" this, we could compromise on it, but Crema just... are uncompromising. They refuse to compromise with us on it, and it's wild
It needs a patch. Really, I cannot stress this enough, anything to do with the battle cameras would require a patch and all patches have to go through certification which takes 3+ weeks, more during the holiday period.
We can only make server changes on the go. This is a client change, so it needs a patch and since we're on more platforms than PC we need to go through certification.
Tsuki, please listen to me.
I'm not asking you to remove it in its entirety. I and as you can see plenty other people are asking for it to be a function you can toggle. Just like egg animations.
If your entire point is, 'we just need time to tweak it', that doesn't matter. It should just be something to toggle on and off to what people fancy. Just like the OST. Musicians put effort into that, to then say we shouldn't be able to turn it off is ludicrous.
The second point is, the game isn't in EA anymore. If you're saying we just need time to tweak it so deal with it... people aren't your beta testers.
I never said that. I said we need time because a new patch needs to be launched and the platform holders need to review it and that takes time, even more so in the holiday period. we've already made changes to them internally. This feature, like all others, was tested internally beforehand and wasn't launched to get the players to act as beta testers.
Tsukki, I mean this respectfully.
I do not suffer from motion sickness. At all. Not cars, trains, busses, or boats. It makes me feel a little off.
On top of that, the moment I saw it, one of my first criticisms was "This is going to make people motion sick!"Surprise surprise, an hour or two after I first saw it, I saw 2 separate users in the discord complain of motion sickness so severe the game was now literally unplayable.
I don't care that no one at Crema felt sick with it, how did none of you see that it had the potential to cause it, and *ask* people. You have an entire discord full of dedicated players. Reach out, find a handful of people with motion sickness, and *ask* them if it makes them feel sick. The fact you didn't even CONSIDER the health effects of the feature is... insane to me. It was obvious to me, and I'm, respectfully, f**king dumb as shit. So how did it escape everyone at Crema?
Different things are obvious to different people. We cannot show WIP features to players without having to go through a lot of legal loops. If you're implying that we're also dumb as sh*t, then I don't know how to continue this conversation respectfully. It already happened, and the important thing now is that we're working on it.
Read moreWe understand that much, it’s just the obstinace that comes with how, imo, particularly YaW responded to criticism. Everyone’s reaction, when you unveiled the feature a month ago, was “ew no I hate that” and you guys got criticism then on it beinf too jarring, too quick, affecting battle.
You seem to have made no changes to the feature in response to THAT feedback. Why should we have faith you will now it’s released? You were told it would make people motionsick a month ago, made no changes, and then were shocked in the discord when people told you they LITERALLY have to QUIT the game because it makes them too sick now to play it.
When you were told how bad it was a month ago, you should have either: - Delayed the feature until it was improves - Added an option to disable it until it was improved, or just give us that option anyway.
Instead you shipped it as is, having already ignored the feedback. Surely you can understand why people are, matter of factly,...
We can't make any changes to features until we publish a patch. Patch 1.2.1 was sent to platform holder for review two weeks ago, but they're still on it, and with the holiday period in-between, they'll take more time than usual.
We can't delay a feature that's already been shipped and in the patch, and the feedback came after it had been shipped and was in the patch. Any change, even adding an option to disable them, requires a new patch, and a patch requires certification.
Like I said, we've already made a lot of changes to them internally following your feedback, now it's only a matter of us being able to launch the patch and have it reach you folks.
I mean people told them of these exact issues a month ago when they first showcased it, coming from people who voiced these criticisms then. They changed nothing about it so I just... why did they ignore feedback?
Why did no one test it and ask "Hm... this feels like it might give someone motion sickness..." and just... find someone who HAS motion sickness and ask them. They just shipped it as is. It feels like no one did any looking at the feature in action, only looking at the code.
We tested it, most of the people at the company saw them (even beyond our QA team and the people who made them) and they gave none of us motion sickness, even though some devs suffer from it. To clarify, all features are tested in action.
Nevertheless, we've already acknowledged the feedback and made many changes to them internally, but they won't be applied to the game until we get to launch a patch, and the build we sent two weeks ago is still being reviewed by the platform holders. We haven't ignored any feedback, we just can't get it to you yet.
Stop trying to change the point. Yes, you're working on it. Please acknowledge the real thing people want: the option to turn it off.
Yes you're working on it. You're asking for feedback. We get it. That is understood. I didn't ask for you to fix it. I asked for an option to opt-out, and so have many others.
I'm not trying to change the point. It's a feature we worked on that we want people to enjoy, that we believe is interesting and adds to the battles, and we want to give it another go and try to make them work well before we consider scratching it off entirely.
feature no one asked for: check
feature not tested: check
feature is disliked by player base: check
devs unwilling to change: check
It was tested. Most of the Crema team saw them and it caused no one here any sort of discomfort nor did we not like them. We have already said we're going to be changing them.
Surprise features can go both ways, but it wasn't done to annoy anyone, let alone the playerbase. We're following the feedback on how to improve them and they'll be different in the next patch.
We've already stated we're working on tweaking them and adapting them so they don't cause anyone motion sickness. We've asked for community feedback on how to improve them and we've followed that. We've also explained we need a patch for this, or anything related to the cameras, and we've been trying to launch a patch for the past two weeks but it's still being reviewed by platform holders.
The Temtem Championship Series (or TemCS, as we like to call it), is Crema's officially-sanctioned tournament series. It will take place in 2023, with the possibility of celebrating future editions based on the success and interest it generates. Players around the world will be split into 3 regions to compete in a set of regional and interregional tournaments throughout the year, battling for Tamer Rating Points (TRP) to qualify for the Temtem World Championship, where the strongest Tamers around the globe will fight for the title of World Champion.
... Read more External link →The Temtem Championship Series (or TemCS, as we like to call it), is Crema’s officially-sanctioned tournament series. It will take place in 2023, with the possibility of celebrating future editions based on the success and interest it generates in this inauguration . Players around the world will be split into 3 regions to compete in a set of regional and interregional tournaments throughout the year, battling for Tamer Rating Points (TRP) to qualify for the Temtem World Championship, where the strongest Tamers around the globe will fight for the title of World Champion.
While we are very excited to announce it, keep in mind this is our first time maintaining an official competitive scene, so while we plan to stick to the format presented below, changes might be made to the circuit in the future to better fit and adapt to the need...
Read more
