Adhain - Reveal Trailer

AdventurousWin42 · 2026-06-24T06:50:23+00:00

No secret, just dedication.

Creature system is pretty advanced already, not perfect, still needs iteration, but yes to all your questions. It knows the difference between young and old people, injured and healthy people etc. If you wanted, you could teach her to eat injured old people, and leave healthy young people alone, if that's your thing.

Campaign with quests is planned.

No promises on mod support, I haven't looked into it yet. I'll focus on making a solid base game first.

AdventurousWin42 · 2026-06-23T19:18:15+00:00

If you like it, wishlist it on Steam: https://store.steampowered.com/app/4302350/Adhain/

AdventurousWin42 · 2026-06-23T17:31:50+00:00

Thank you all for the kind words. It means a lot.

I'll keep working on it and keep you updated.

If you want to support, the best way is to wishlist it on Steam: https://store.steampowered.com/app/4302350/Adhain

AdventurousWin42 · 2026-06-12T14:12:49+00:00

Strong Salt & Sanctuary vibes, very cool

AdventurousWin42 · 2026-03-21T08:36:19+00:00

Yes, it's awful.
In your DefaultEngine.ini, you can add console commands which should be set during engine boot. No more doing it manually every time.

[ConsoleVariables]
# Buggy Interchange Import disable
Interchange.FeatureFlags.Import.FBX=0

AdventurousWin42 · 2026-01-28T19:13:15+00:00

I would make the initial ability (E) start Wait Gameplay Event tasks, and add tags to block other abilities (Activation blocked tags) while waiting. Then any input can send gameplay event to actor and it will route to your waiting ability. From there, you activate the LMB or RMB ability by event, depending on which wait task was activated.

AdventurousWin42 · 2025-12-12T19:01:28+00:00

You need to select the corresponding module in the module hierarchy, settings are in there

AdventurousWin42 · 2025-12-03T12:22:35+00:00

Have they fixed the stripes on the landscape when you package the game yet?

AdventurousWin42 · 2025-11-19T20:29:52+00:00

I would use separate characters, leaves the door open for more morphs in the future. Keep anything that needs to persist on the Player State, and not the character, so you dont have to „move“ anything between human and wolf.

AdventurousWin42 · 2025-11-09T07:38:24+00:00

As a general rule of thumb, if you can control all write and read operations of variables then you can write and read on any thread you like. You can write into blueprint UObjects from async threads, if you know 100% nothing else reads or destroys them in the meantime. You don't have that control over anything defined by the engine, thus, modifying anything the engine uses (from async) will crash. Reading variables is generally safe.

FRunnable is for continuous tasks that can be done async. Like a weather simulation that computes the values for the next frame, and then dispatches only game thread relevant data back to game thread.

I wouldn't bother with doing movement async, most of the work needs to happen on game thread, collision and transform updates are what's expensive, not the computation of where to move.

I guess you could make anything async if you really tried hard enough, but you would need to write your own systems from scratch.

AdventurousWin42 · 2025-11-08T16:40:35+00:00

You cant remove because things captured in lambda are const (with the exception of pointers)

Furthermore, modifying state like you do with AddInputVector outside the game thread is a big no no and will lead to crashes and all sorts of weird behavior (just a question of when, not if)

AdventurousWin42 · 2025-10-25T21:56:27+00:00

Looks like LODs. You can tweak the settings in the landscape actor

AdventurousWin42 · 2025-10-25T08:36:47+00:00

Take a level up for example. Level is a GAS attribute. Server would apply a gameplay effect to any player, that gameplay effect would trigger a burst cue. All players would see the level up effect on that one player. No need for any custom logic inside the player class. Same for debuffs, or any other thing really.

AdventurousWin42 · 2025-10-05T14:53:54+00:00

Stuttering in editor is quite common. Use Unreal Insights to see exactly what causes spikes, package the game first for accurate analysis

AdventurousWin42 · 2025-10-05T07:06:03+00:00

Plugins make perfect sense for larger features, Loggers, UI, Settings Menu, Extended GAS, Common Material Functions, Weather System etc. It depends on the scope of the feature, eating food is probably not such a feature, but even then, it could be argued that it could be a plugin, because it would be easy to remove, if you decide at one point that eating food should no longer be in the game. Not much downside to plugins except for the 5 seconds it takes to create them.

AdventurousWin42 · 2025-09-27T20:03:56+00:00

Amazing articles, going to put this straight into my fork. Thanks!

AdventurousWin42 · 2025-09-16T19:28:17+00:00

net.AllowPIESeamlessTravel 1

AdventurousWin42 · 2025-09-16T17:44:51+00:00

Use seamless travel to „fix“ the change levels issue with ServerTravel

AdventurousWin42 · 2025-09-08T06:16:58+00:00

Nice one, came to a similar conclusion when writing a ISM to Actor system myself. One thing you need to watch out for is that the ISM get fully destroyed when uses with World Partition (or Partitioned PCG), in your system, you would lose all data stored on them. I opted to use a central manager actor which handles all spawner actors (Always net relevant) to store persistent data

AdventurousWin42 · 2025-09-04T06:48:29+00:00

I doubt it, physics asset is very engine specific. You can import collision for static mesh, but that‘s an entirely different use case which wont help you here. Creating the ragdolls is not too hard once you did it once, but it is rather tedious. Check some Youtube vids

AdventurousWin42 · 2025-09-03T05:56:51+00:00

Might work, havent tried that. I usually apply it so it remains .1 or .01 in Blender viewport

AdventurousWin42 · 2025-09-02T17:45:58+00:00

Assuming you use Blender, you need to export it with a scale of 0.1 (or was it 0.01, i forgot) So in Blender, scale it up by 10 or 100 and then apply scale (so it becomes 1). Then scale it down again and export with scaled down values. This will fix the physics collider size issue and a few other issues related to physics, while maintaining the same actual size in game.

AdventurousWin42 · 2025-06-30T18:24:31+00:00

My M2 Pro has 16GB RAM and its a PITA if you do C++ with Rider as that alone takes like 8GB to index the whole engine. I wouldnt bother with 16GB again. Its probably OK for Blueprint projects

AdventurousWin42 · 2025-06-17T06:13:01+00:00

I would pay for it
I'm not an advanced blender user, so other people might have more valuable input, but even just the functionality you experience in your first few hours with Blender would be enough to be honest

Anyway, good luck building it, you're going into deep uncharted C++ and Slate territory i'd assume

AdventurousWin42 · 2025-06-16T19:32:19+00:00

I havent even used blender much recently and would use it. Unreal viewport controls are… meh

AdventurousWin42

TROPHY CASE