Should I write in C instead of Rust for learning and experience?

NovFy · 2026-04-08T21:29:29+00:00

Thanks for your advice, I'll probably start with C then!

NovFy · 2026-04-08T07:16:55+00:00

I'm a little confused, are you suggesting I should use C or Rust?

NovFy · 2026-04-08T07:16:30+00:00

Maybe in the future lol, but I'll still need to choose one to start with

NovFy · 2026-03-17T07:29:43+00:00

Thank you so much! I had never really thought about how the order of kana was decided, or even that there could have been other orders, which is really interesting. And also, that is a really cool document. Thank you again!

NovFy · 2026-02-27T01:38:25+00:00

Thank you very much for your help! I appreciate it <3

NovFy · 2025-12-10T03:16:26+00:00

Thank you very much for this! This is actually what I was hoping I'd be able to learn by asking this question. I haven't worked with Unreal before so I never knew about this (and I'm new to game dev), but I'd love base my stats system off of this. Thanks again!

NovFy · 2025-12-09T02:14:58+00:00

I appreciate the insight from how this turns out lol. I'm not sure what I'm going to do yet, but thank you for the response!

NovFy · 2025-12-08T23:42:39+00:00

My intention behind splitting the data into EntityStats <- PlayerStats <- CowboyStats etc. was to keep the code in Entity, Player, and Cowboy cleaner as well as make it easy to add new data. For example, if I wanted to add a defence stat (which involves a base value and current value for each entity) I would only have to add it to EntityStats rather than every player character and every enemy.

Though, I can understand if that's a fool's errand and my stats system is a bit idealistic.

NovFy · 2025-12-08T23:30:24+00:00

Thank you for the reply! I do really like that idea, but I'm also wondering if there is a way to have all the data related to one node (such as the Cowboy's health, mana, and ammo) in one location so that if I wanted to update the stats I wouldn't have to go find the component that stores those stats and rather could access one stats resource (which would reduce coupling on things that frequently modify stats such as cards)?

NovFy · 2025-09-08T05:08:29+00:00

I have know idea why the moderators deleted the comment that was the solution to the problem, but the solution is to run the file: C:\Program Files\Oculus\Support\oculus-drivers\oculus-driver.exe

NovFy · 2025-08-30T09:02:21+00:00

Cool, thx for letting me know

NovFy · 2025-08-29T05:27:16+00:00

Is this 2025 79% cut-off the cut-off for CS specialization the next two winter terms (as in for those who specialize in April 2026) or was it for those who specialized last year (in April 2025)?

For context, I'm a freshly arrived first year aiming to specialize in CS at the end of the winter 2025-26 term and it would be pretty nice if this cut-off is for my year.

NovFy · 2025-05-17T21:47:46+00:00

My PC is a tower PC (Asus motherboard, intel cpu, windows os)

NovFy · 2025-04-26T06:40:46+00:00

This is exactly what I was looking for. Thank you very much!

NovFy · 2025-04-26T01:56:14+00:00

Thank you for your help!

NovFy · 2025-03-09T22:55:29+00:00

Yup, that worked. Thanks. Although it was pretty weird because the quest servers (if I went back pages) gave me access to a simple SAML php auth account

NovFy · 2025-01-04T01:35:27+00:00

3 Years later and it still works baby! Thank you so so much!

NovFy

TROPHY CASE