robhol Posted May 20, 2009 Share Posted May 20, 2009 (edited) I've decided to release this program. (Originally intended for personal use.) ClientLuaConverter (CLC) is a program that simplifies and nearly completely automates the compilation of client-side scripts in order to minimize file sizes and prevent leechers from stealing your scripts. It provides a simple interface where you can easily select individual resources to compile, or bulk compile your entire resource folder. It also has a batch job function. By creating a batch file, you will be able to easily convert any given list of resources with just a few mouse clicks. The program compiles client-side files only, and leaves the source files intact. The program is no longer offered nor supported. Edited July 27, 2009 by Guest Link to comment
robhol Posted May 21, 2009 Author Share Posted May 21, 2009 Version 1.1 released. This version has improved error handling and user interaction. Link to comment
50p Posted May 21, 2009 Share Posted May 21, 2009 I haven't tried it but I think you should make applications with .NET 2.0 because not everyone has .NET 3.5 installed. It can be useful for some people : P Link to comment
robhol Posted May 21, 2009 Author Share Posted May 21, 2009 And if I were using 2.0, people would still whine because not everybody has 2.0, I suppose.. Anyways, this uses LINQ features which were actually not implemented until 3.5. If you guys haven't gotten the last version of CLC (1.3) yet, do it now, by the way. I have no idea how I missed it, but the older versions had a nasty bug that caused it to randomly not give any output... It SHOULD be fixed by now, but let me know if it isn't. Link to comment
50p Posted May 21, 2009 Share Posted May 21, 2009 Ah, LINQ... so it won't be useful for me. Anyway I think .NET 3.5 is still too new to use it. Link to comment
DutchCaffeine Posted May 23, 2009 Share Posted May 23, 2009 For windows vista users, run this application in administrator mode. If you don't do it, it won't completely work. Link to comment
robhol Posted May 24, 2009 Author Share Posted May 24, 2009 Is anybody actually getting it to work? I've only talked to one guy who uses it, and it doesn't for him, although everything works to perfection here. Link to comment
Winky Posted May 24, 2009 Share Posted May 24, 2009 Could you provide a zipped/rarred/tarred version, without the installer? Link to comment
Stoney Posted May 24, 2009 Share Posted May 24, 2009 No success on Windows 7 beta. It says that conversion was completed successfully but all it actually does is edit the meta.xml file. It doesn't create the clc file. Maybe I'm missing something... Link to comment
robhol Posted May 24, 2009 Author Share Posted May 24, 2009 Could you provide a zipped/rarred/tarred version, without the installer? Well, aren't we picky! Here. Link to comment
[DKR]silverfang Posted May 24, 2009 Share Posted May 24, 2009 No success on Windows 7 beta. It says that conversion was completed successfully but all it actually does is edit the meta.xml file. It doesn't create the clc file. Maybe I'm missing something... I get the same problem as my friend Stoney here. All that I can see is happening is an edited meta.xml and a meta.xml.bak, I cannot see any lua.clc file anywhere. This is on XP. Link to comment
Winky Posted May 24, 2009 Share Posted May 24, 2009 Could you provide a zipped/rarred/tarred version, without the installer? Well, aren't we picky! Here. It seems it works here on Windows Vista x64. You should update your manifest file, the application should be starting with Administrator Rights on Windows Vista. Link to comment
Phat Looser Posted May 24, 2009 Share Posted May 24, 2009 It doesnt work on any XP version when the path to the files to compile contains spaces. It does compile stuff as soon as the path is "valid". Have fun. Link to comment
50p Posted May 25, 2009 Share Posted May 25, 2009 It doesnt work on any XP version when the path to the files to compile contains spaces.It does compile stuff as soon as the path is "valid". Have fun. The thing is that to compile lua code with luac.exe you have to pass path to it not as string with quotes (eg. "hell world.lua") but without quotes (eg. hello world.lua). The problem is that the first parameter is file you want to compile (which would be: hello, which doesn't exist) and the second param is the output file (in this case world.lua)... I haven't use this tool (due to .NET 3.5) but I'm pretty sure the problem is in the paths and the compiler probably outputs some errors. Link to comment
robhol Posted May 25, 2009 Author Share Posted May 25, 2009 If that's true and Luac doesn't actually accept quotes, you have to move your resources to another folder to CLC them. Link to comment
50p Posted May 27, 2009 Share Posted May 27, 2009 I just checked and luac.exe does support paths with quotation marks, so the problem must lay somewhere else. Did you release source code for this "tool", robhol? Link to comment
robhol Posted May 27, 2009 Author Share Posted May 27, 2009 (edited) No, I didn't, and won't, probably... are you completely sure you have installed 3.5? Edited May 28, 2009 by Guest Link to comment
50p Posted May 28, 2009 Share Posted May 28, 2009 No, I have 1.1, 2.0 and 3.0 versions of .NET. I've never had 1.5 nor 3.5. If I'd love to compile it I'd download 3.5. I was wondering what you used LINQ for Link to comment
Mr.Hankey Posted May 28, 2009 Share Posted May 28, 2009 LINQ contains a few XML functions i guess that's what robhol used it for Link to comment
50p Posted May 28, 2009 Share Posted May 28, 2009 I used .NET 2.0 to parse meta.xml to get files included in resource and it's not that hard. Just one loop. If you used C# than take a look at this .NET 2.0 code, robhol: ArrayList files = new ArrayList( ); if( File.Exists( path + @"\meta.xml" ) ) { FileStream fs = new FileStream( path + @"\meta.xml", FileMode.Open ); try { XmlTextReader reader = new XmlTextReader(fs); while (reader.Read()) { reader.MoveToContent(); if (reader.NodeType == XmlNodeType.Element && reader.Name == "script" ) { files.Add(reader.GetAttribute("src")); } } fs.Close(); return files; } catch { } } This is a piece of code that I used to get all the script files included in meta.xml and it's C# .NET 2.0. Don't choose the easiest way because you will never learn harder things. Besides, .NET 2.0 is for wider audience. Link to comment
robhol Posted May 28, 2009 Author Share Posted May 28, 2009 (edited) Yes, it makes XML handling easier. My job is not to accomodate every last person not wanting to keep his system updated. There's no real reason to not download .NET 3.5. Also, it's not like I get paid for this program: if people don't use it, I don't give a - I just released it because it could help people avoid getting their script stolen. Edited May 28, 2009 by Guest Link to comment
Prieto_Galletini Posted July 11, 2009 Share Posted July 11, 2009 ok one question does the script i mean the client side script does it need some coding inside to work cause im getting a error and it only says failed to get file blahbla/resource so does it need to have certain code inside it?? Link to comment
robhol Posted July 11, 2009 Author Share Posted July 11, 2009 (edited) I don't know why this program is fucking up left right and center, but works for me. It would kinda help, though, if you actually gave me the error message. Does CLC tell you of any errors, warnings or exceptions? Edited July 15, 2009 by Guest Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now