UE4SS

> Then I'm still stumped. I've been looking around and haven't found any solution yet. Seems I'm the first to encounter this? You're the first that I'm aware of. Hopefully...

> Just noticed this in the README file....  These are the requirements for building UE4SS from source, not for using the binary files in the releases section to mod...

> > It means PS is failing in `read_image` in `patternsleuth/src/process/internal.rs` for an unknown reason. > > Is this in a `.dll` file or is this in a `.lua` file?...

The links for the dmp and log files are broken. Unless they are prohibitively large, you should be able to upload them directly to github by dragging them to content...

We don't currently support MapProperty (aka TMap) in Lua at the moment. TSet has recently been implemented in C++ which TMap requires so hopefully we'll get proper support for TMap...

> I wonder if this can be made more ergonomic and less error prone, e.g. instead of passing the function name to call you pass an event I agree that...

There is no type-checking to make sure the param types of `Function to Call` match the param types of the hooked function. What happens if the mod supplies a `Function...

For implementing type-checking of params, see these links: https://docs.ue4ss.com/lua-api/classes/ustruct.html#foreachpropertyfunction-callback https://docs.ue4ss.com/lua-api/classes/property.html#isapropertytypes-propertytype https://docs.ue4ss.com/lua-api/table-definitions/propertytypes.html?#propertytypes

We should probably implement an overload to `Property:IsA` that takes an actual UE property type because the current one only takes the `PropertyTypes` custom Lua type which means testing one...

@Okaetsu Maybe we can put the new `IsA` overload in your PR ? To keep things simple, and it's a related and dependent feature anyway.