Here are some screenshots from the server at https://t.co/3a6itjbrHB (Pocket Edition/Win 10 Edition SkyWars running on a modded native Minecraft server)
@MCMrARM@HexRaysSA We appreciate the feedback concerning our latest EULA. We are not uncomfortable with competition but rather unfair comparative test results getting published without us having a chance to scrutinize the results or the methodology. We will get the EULA updated accordingly. Thanks!
@brinlystorm@HexRaysSA@dogboltorg I don't think this change is malicious, I assume it is just the fact the company has grown and they got actual lawyers to write the EULA for them; nonetheless I find this disappointing.
.@HexRaysSA has updated the EULA for IDA Pro 8.3 and I took an issue with it.
The new EULA seems to prohibit the use of the software by developers of "competing" software or for benchmarking/comparisons.
There are other parts of the EULA some users may not like, but these are not as bad as this point of the license (eg. the 10.1 Data Protection section allows automatic data collection, however this is hardly a rare thing in EULAs these days). EULA is here: https://t.co/vvzKl30Dvp
I can't tell how much of this is actually legally enforceable (eg. the marketing claim might not be), nonetheless I still urge @HexRaysSA to remove this paragraph from their EULA if they truly believe in their product.
@GFPCoder @AjGamingPH2@TuberCraven@zhuowei The binary format seems unstable, so I think a launcher that would aim to solve this would need to rewrite the binary files so the chance of the shaders breaking in the next minor update aren’t that high. Any thoughts on how you would like this solved?
@GFPCoder @AjGamingPH2@TuberCraven@zhuowei Hey, Zhuowei messaged me about this yesterday. How are you currently editing the shaders? They seem to be now embedded in a binary file in the materials folder (why the hell), are you editing them with a hex editor then repacking the game currently?
@discord Hello! We have submitted a partner application for the Toolbox server (450367979310284801) over 2 weeks ago (I think we submitted it around 12h after the program was relaunched!). Any reason for that or is this normal? Thanks!
@itsmomo_dev @qwertyoruiopz@gsora_@h0m3us3r@Aunali1 This was the first thing that we fixed on the T2 Macs; it didn't work because, Apple would follow standards? No way in hell!
@itsmomo_dev @qwertyoruiopz@gsora_@h0m3us3r@Aunali1 NVMe has been supported since like a year, and it's already in the upstream Linux kernel (5.4 or 5.3).