Ark Dev Kit : Features request [New Procedure 4/11]

[Lifefire]

@;605320

Never going to happen. The core code-base changes between .5 and .9(and this goes for any engine really, later than 4.7) alone are too great to be futzing around with an already working engine and a game that is used by hundreds of thousands of people. They have an entirely custom engine and they pull features they want or changes/fixes they need from newer engines, no need to deviate.

This is already a thing? Either directly or workable, I’m pretty sure there’s two means of determining this.

Also not going to happen. The core of ARK is done entirely in C++… you can’t just turn C++ into graphs either literally or ethically due to the inherent performance/optimisation gains from working largely in native code and some things just can’t be done in Blueprint. The best you’re going to get is when they decide to do new mechanics/features in blueprint, which they started doing a couple of months back.

-WM

i’ll elaborate a little bit on what i meant for each one…

the first, yes it’s a custom dev kit, which means more updated features can be added from newer engine versions…

the second, i have looked for weeks and short of creating my own xp variable i have not been able to locate one, if you know where it is located can you please share that with me as it is a critical function in my ui mod…

the third, i meant exposing more of the core variables to be “blueprint callable”, they are already exposed in the “defaults” section of bps but being able to call them even if they are read only would increase everyones modding capabilities.