![]() But I'm determined and sometimes that's a strength. I don't necessarily disagree with the wisdom of the crowd here. In comparison to complaints about workflow/issues using package manager as example, how many users complain about people hacking into their unity remotely? The answer to that question alone answers why this just wont ever be a sensible time sink (Even if the logic behind why this is something to work on was sound - which it is not for reasons stated by a few users already)Ĭlick to expand.Re: protecting IL2CPP output executables from third-party modification. This just does not stack up in the realm of important anythings, to focus on compared to the many things already needing attention in comparison (and rightfully so). Why out of all the ideas would this make sense to prioritise (or even give thought to) when there are things that can actually benefit majority of users that still need to be worked on, like fixing package manager workflow issues or optimizing the way features are worked on and released to minimise wasted work/features getting killed etc etc. ![]() ![]() I think overall its just not a sensible suggestion for all the reasons already stated, in addition to the following : In reality though, absolutely agree with on all points he has raised. a better application would be performance or just general terrible code optimization.Ĭlick to expand.Wait wait wait, are you suggesting this is not something we should be pushing for them to add to the hub? What if I want to keep up with beanie-baby prices WHILST developing in unity? Outrageous! /s I mean really, if Unity could make a magic tool that could detect if user code is doing something unintended. No remote "hacker" is going to hack into your computer and make Unity do bad things.īut, again, none of this stuff is impacted in any way by a "integrity check" run by the app or hub. If this causes problems, it is because of a choice the user made (at some point). Running remote plugins often requires settings in the package manager and even sometimes keys for the server. You have to install something, or specifically write something to do local file damage and even then you are going to have to actively bypass local sandbox security settings or write things specifically to get around local permissions settings. There is very little damage one can do using Unity by accident (apart from build folder, if that is still a thing). Click to expand.Yes, that is what I meant by "operator".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |