- Posts: 1164
- Joined: Mon Aug 31, 2015 10:31 pm
Cause if it can, the client file could be moved-away/renamed using Unreal instead than forcing the user to close UT and move-away/rename the file manually to then restart UT and reconnect to the same server.
- Posts: 3765
- Joined: Fri Jan 14, 2011 1:53 pm
- Personal rank: -Retired-
I totally get what you are saying but there are safer ways of doing this. It's being worked on currently and a good solution is coming at some point. Hang in there.
- Posts: 577
- Joined: Tue Jun 20, 2017 1:00 pm
- Personal rank: ⚋⚊⚌☰⚞⌖⚟☰⚌⚊⚋
Either ways, even that being the case, there are other ways to solve the mismatches problem, and that is by avoiding them altogether.
Search what developers did in PHP before namespaces were implemented, and that should give a strong clue how developers should name their packages to avoid this problem altogether, because regardless of mismatching or not, having 2 packages with the same name from different authors is always a big problem regardless.
The same goes for classes.
Textures and other static resources are rather immune to this given that they have their own package and group which already serve as namespaces.
- Posts: 1963
- Joined: Sat Sep 17, 2011 4:32 pm
- Personal rank: Dame. Vandora
- Location: TN, USA
Meanwhile, it's still manageable manually by client side. There are only 1 file that is server side only so the client doesn't have to deal with the credit issue, which that is already posted here in UT99.org.