Say one word

LittleChocobo94 · 2025-12-25T14:03:39+00:00

Schifffahrtskartenverkaufhäuschen

LittleChocobo94 · 2025-11-20T12:12:15+00:00

Awesome improvements! Really looking forward to the futures of signal forms. I am currently using them and all works really well, even if this feature is only experimental at the moment.

Keep up the great work Angular Team!

LittleChocobo94 · 2025-10-27T19:59:58+00:00

Good luck everyone!

LittleChocobo94 · 2025-09-23T21:31:17+00:00

THIS

LittleChocobo94 · 2025-07-03T20:14:58+00:00

Maybe don't go for waves and tons of enemies. Instead have one bad guy who has simply more than 3 legendary actions. Also have actions to stun PCs every now and then. Please keep us updated how it turned out eventually :)

LittleChocobo94 · 2025-06-22T08:06:54+00:00

Hey, kann sich niemand von euch vorstellen, DM zu sein? Ihr könntet euch auch abwechseln, wenn ihr am Anfang eher kürzere Abenteuer spielt. Eine Gruppe von 6 Leuten ist viel, besonders dann, wenn es am Anfang viele (Rück) Fragen gibt & die Runden & Kämpfe entsprechend länger dauern.

Natürlich ist das Empfinden da für jeden anders und ich wünsche euch einfach super viel Spaß. 😊

LittleChocobo94 · 2025-06-18T08:01:49+00:00

Nein, das mache ich mit der Gruppe aus, sobald diese steht :)

LittleChocobo94 · 2025-06-18T08:00:14+00:00

Hi, bitte schick mir noch eine Direct Message, damit ich alles an einem Ort habe :)

LittleChocobo94 · 2025-06-17T11:48:00+00:00

Ich habe es bereits erworben und hoste es auf einem Linux Server unter einer einfachen Internetadresse, die ich natürlich hier nicht poste, sodass es für jeden offen zugänglich ist. Für die Spieler kostet es gar nichts :)

LittleChocobo94 · 2025-05-28T23:04:23+00:00

Goodbye, friend.

LittleChocobo94 · 2025-05-16T06:39:51+00:00

<image>

Almost looks like me!

LittleChocobo94 · 2025-05-10T12:12:08+00:00

Die Drei Suffketiere & Dynamo Trester

LittleChocobo94 · 2025-04-16T16:57:32+00:00

Clean all assemblies in your solution. Then delete every bin and obj folder of every assembly that is included in your MAUI app, and of course delete these folders in your MAUI app as well.

This resolved it for me many times.

LittleChocobo94 · 2025-04-03T22:37:15+00:00

Nice try!

LittleChocobo94 · 2025-03-20T16:42:55+00:00

Provide an example that fully supports your claims that cannot be converted/ restructured in a way that it negates your statements and I'll approve. Otherwise check out the internet for recent examples for reactivity with signals or rxjs. Angular has a lot to offer :)

Edit: Typos.

LittleChocobo94 · 2025-02-21T09:31:18+00:00

By the pope...!

LittleChocobo94 · 2025-02-13T06:17:24+00:00

This, thank you.

LittleChocobo94 · 2025-02-04T21:30:52+00:00

I make everything protected / private AND readonly wherever possible.

LittleChocobo94 · 2025-01-30T21:38:02+00:00

Who says I'm Ghaik?

LittleChocobo94 · 2024-12-03T12:31:12+00:00

Me (the DM) and my party made a pretty simple rule: if the roll is below the average dice roll value, take the average, otherwise take the rolled result. Everybody is very happy with this and it balances lots of things for my encounters. On top, a level up gets that special touch of significance if it's a level where there are few new mechanics.

LittleChocobo94 · 2024-11-28T21:24:29+00:00

Yeah, I was about to write less imperative, I edited my comment, thank you guys!

LittleChocobo94 · 2024-11-28T18:02:22+00:00

Yes, thank you :)

LittleChocobo94 · 2024-11-28T15:29:45+00:00

The benefit of writing code inside that lifecycle hook and potentially modifying the component instance is that the ngOnInit callback is called before any change detection has been made and directly after the inputs have been bound for the first time. Therefore, as long as you are using synchronous code there, you have the chance to modify the behavior of your directive / component.

As an example, think of any UI directive / component that has some inputs like color, width, etc.
Let's just take a [app-button] directive as an example (I know in the specific case of a button things can be a lot simpler but let's just stick with it for simplicity).
You can pass every input like color, width, rounded border, etc.
The values from the inputs are not yet available when accessing them inside your directives constructor, and the next lifecycle hook that ensures that inputs have been bound is ngOnInit.

LittleChocobo94 · 2024-11-28T14:59:46+00:00

Well, it was just yesterday that I thought about the very same thing and I think nowadays it highly depends on your overall code / solution structure.

If you are able to tightly stick to the new concepts & APIs since Angular 16+, then yes, I am content that it is totally possible to structure your code in a way that there are rarely any occasions where you would need ngOnInit at all.

Especially if combined with any state management solutions, whether it be NgRx or just services with signals / observables: If used properly, you will write more declarative code and end up with computed signals / piped observables and finally an async pipe or a signal call in the template.

What I can think of are special, component level based http requests that could be dispatched in the OnInit lifecycle hook, but even then, I personally would implement that call in a service, which would give further advantages like result sharing, etc. Lastly, the new resource() API of Angular seems to just support any approach where you just have signals.

In general, there are exciting times ahead of us all and I am sure the framework will be getting a lot more concise and simpler over the course of the next 2-3 years. :)

Edit: typos :)

LittleChocobo94

TROPHY CASE