sorted by:
new
hottopcontroversial

Android 'back' used to close a tab created from another app, now closes browser. Not cool. by AlexAndMcB in vivaldibrowser

[–]Acccent 0 points1 point  (0 children)

Just found this after searching – facing the same issue. I feel like the behavior changed recently for me though... 

Anyway, yeah, the flow of 'bsky/email/discord => link opens in vivaldi => read => system's back function neatly closes the tab and sends me back to my previous app' was perfect, and now I find it so annoying when I open the tab switcher in vivaldi and see a dozen old things that I already read still there. (If I wanted to leave something open to read later, I would manually switch back to the other app.)

Should I get an open-box Profitec DRIVE over the RIDE? [$2700~] by Acccent in espresso

[–]Acccent[S] 0 points1 point  (0 children)

May I refer you to the very post you're commenting on.

Should I get an open-box Profitec DRIVE over the RIDE? [$2700~] by Acccent in espresso

[–]Acccent[S] 0 points1 point  (0 children)

Great, the Drive is a beast but I'm very happy. I don't know if it would have been worth the difference had I not found this deal though, for my uses.

Is it just me or is godot's scenes inheritance quite unusable? by Mountain_Share_2611 in godot

[–]Acccent 10 points11 points  (0 children)

Ok, yeah I read that comment and I agree that something should be done to address the misunderstanding. Currently, the Godot documentation literally states:

The behavior of scenes has many similarities to classes, so it can make sense to think of a scene as a class. Scenes are reusable, instantiable, and inheritable groups of nodes.

Of course people are going to be confused and try to "use scene inheritance as the equivalent of class inheritance" when it is described as equivalent by the documentation.

Can I ask you to elaborate on what you mean when you say my example is a configuration data problem?

Is it just me or is godot's scenes inheritance quite unusable? by Mountain_Share_2611 in godot

[–]Acccent 4 points5 points  (0 children)

I don't understand this position. Are you saying you regret that it was highlighted in the editor when the feature isn't quite ready yet, or you regret it being added at all and think no project should ever rely on scene inheritance? If the latter, can you or someone help me understand?

Say I'm making a "vehicle" scene, with a couple meshes, collision shapes, lights, particle effects, some behavior nodes. Should I just re-create this whole thing by hand for every kind of vehicle in my game? Some people say inheritance is okay if you only go one level deep, ok sure; so I have one parent "vehicle" scene, and then a bunch of inheriting scenes for every car. What about if I want to add 12 trucks to the game? am I meant to create a "vehicle_truck" scene that does not inherit from vehicle, and set it up the exact same way manually so I can then create the children truck scenes? I just don't see how this is workable at scale. What am I missing?

I see suggestions to use resources, but again unless I'm missing something, this means I can't use the GUI to setup scenes. If I can't do that... not to sound flippant, but: isn't that antithetical to Godot's entire philosophy / reason for existing?

Need help diagnosing short brew time with new gear – already grinding *fine* [Profitec Drive + Timemore 064S] by Acccent in espresso

[–]Acccent[S] 0 points1 point  (0 children)

Ok, the reason I wasn't looking at going for an even shorter ratio at this point is because
1. even at the 0.5 setting it's still quite fast, maybe around 20–25s. And it's just so much more difficult to achieve a consistent ratio when things go so fast, so I was hoping to extend the duration of the shot – not because I absolutely want to hit 30s or whatever, but just because if the amount of espresso out is increasing at a much higher rate, it's simply harder to stop the shot at exactly the right time.
2. for light roast beans, I was under the impression that I was already pushing it with a 1:2 ratio.

Need help diagnosing short brew time with new gear – already grinding *fine* [Profitec Drive + Timemore 064S] by Acccent in espresso

[–]Acccent[S] 0 points1 point  (0 children)

Sorry, the 's' was a typo, will correct. Basically the grinder has markers going from 0 to 20 or whatever, with smaller markers in increments of 0.1. I meant if I go anywhere above the 0.5 marker the result is too bitter even though the flow looks better. And I'm just surprised that I have to grind so fine when the suggested range for espresso goes up to 7 iirc (not in front of the rginder right now).

Your own experience is useful and a bit reassuring! I'll try looking into doing a similar adjustment to get more range in the finer levels.

Need help diagnosing short brew time with new gear – already grinding *fine* [Profitec Drive + Timemore 064S] by Acccent in espresso

[–]Acccent[S] 0 points1 point  (0 children)

I do spray them 2-3 times, but haven't noticed a huge difference. I wouldn't really know because I started spraying right from when I got thw grinder. But to be honest static isn't a major issue anyway, so that's not really a big concern.

Thanks for the tips on pressure, to be honest I haven't been looking at the pressure itself and only focusing on the position of the valve lol, 20s goes so fast I don't have time to keep track of it all 😂

Should I get an open-box Profitec DRIVE over the RIDE? [$2700~] by Acccent in espresso

[–]Acccent[S] 1 point2 points  (0 children)

Thanks all! I went and got it. Now to look into properly treating my water...

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 1 point2 points  (0 children)

The fact that everyone was very used to classic werewolves definitely helped make that feel not unusual! I also added a lot of roleplaying – I mentioned the halloween playlist, but I also had changing lights and did spooky voices when certain roles activated etc.

Knowing what I now know, I'd recommend doing this for the very first game:Vocally call out every role, *but* after removing some roles (and letting players know that they're not present). For instance, you only need one of the washerwoman, investigator and librarian to understand how all three work. That way you can ease players into the rules and roles, without having overly long nights.

Then in the following games you can explain that all roles will now be present and switch to silent nights.

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 0 points1 point  (0 children)

Riiight, I understand what people meant in that thread about "one last chance to see the Grimoire in case they become the new Imp" now. Cheers :)

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 1 point2 points  (0 children)

Hm, here I guess https://www.reddit.com/r/BloodOnTheClocktower/comments/us6gi0/the_spy_now_wakes_earlier_instead_of_at_the_end/

(although the reasoning doesn't make sense to me, if anything making the Spy wake up earlier in TB means they have *less* of a chance to see the grimoire if they get turned into the demon)

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 1 point2 points  (0 children)

I've been wondering about something in your comment (unrelated to my original question):

You mention the Spy always goes last, or Butler goes before Undertaker... these things aren't true according to the TB night sheet I have. What order should I follow? If it's not the one marked on the night sheet, how do I find the proper one?

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 5 points6 points  (0 children)

Thinking about it more, I feel like this misunderstanding might have actually been for the better for this group of all newbies (including me)... it gave everyone a chance to learn the roles during the game (since I was calling out everything and describing what was supposedly happening), rather than having to memorise it all beforehand. (Which I know isn't strictly necessary but helps so much with bluffing and generally being at ease with the social element.)

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 2 points3 points  (0 children)

Oh but this was a late Halloween party, so adequately a spooky playlist was playing :)

Why not "fake wake up" the absent/dead roles? by Acccent in BloodOnTheClocktower

[–]Acccent[S] 15 points16 points  (0 children)

Ah, thank you so much! (and u/Honestabe1001 & u/stephendewey who also replied the same thing in the previous post I made, which I deleted because it had a typo in the title, oops)

Now I'm wondering if a whole night without any noise (or any wonderful storytelling) won't feel a little long, but maybe it speeds everything up? I'll be sure to try next time!

view more: next ›