• What Are You Working On? -- October 2012
    585 replies, posted
[QUOTE=vercas;38060593]classes, switch statement, line decorators, table and list comprehensions, etc.[/QUOTE] The only thing that sounds useful there is classes; but you have so much more power with metatables.
I had a so-original-noone-made-this-yet idea again, colors for items! Added some stripes, because they make everything look awesome. I am quite satisfied about the result, nothing big, but I think it looks cool. [IMG]https://dl.dropbox.com/u/7659139/Facepunch/colors_forstuff.png[/IMG]
[QUOTE=Matt-;38060850]The only thing that sounds useful there is classes; but you have so much more power with metatables.[/QUOTE] Those classes are obviously made with metatables.
So I told myself that I'd add a 12x ballistic scope to Customizable Weaponry in GMod 13 as soon as it'd be close to release and render targets would get fixed, and so I did. [media]http://www.youtube.com/watch?v=hi9syNz1ZJM[/media]
[IMG]http://puu.sh/1fw5e[/IMG] Was it worth it? :S (Imma change the icons a bit)
[QUOTE=vercas;38062292][IMG]http://puu.sh/1fw5e[/IMG] Was it worth it? :S (Imma change the icons a bit)[/QUOTE] looks awesome, xm simple bug - "W" clipped :O
[QUOTE=vercas;38062292][IMG]http://puu.sh/1fw5e[/IMG] Was it worth it? :S (Imma change the icons a bit)[/QUOTE] Does it have kick flags? aswell as the default ones like ban, slap,slay, immunity ect, i don't really understand what the flags give.
[QUOTE=vercas;38060139] [editline]asd[/editline] My builder is also multithreaded and multicore. :D[/QUOTE] Seems you don't know what a core or a thread is. Because tokenizing strings needs 4 cores of processing power right? Sounds totally legit.
[vid]http://puu.sh/1fAiu[/vid] I'm late the the physical bullets party :( Was at least very fun to make.
[QUOTE=BlackAwps;38065809] I'm late the the physical bullets party :( Was at least very fun to make.[/QUOTE] Would've looked better with the spectator on the bullet in first person.
[QUOTE=BlackAwps;38065809]-vid- I'm late the the physical bullets party :( Was at least very fun to make.[/QUOTE] The programming waywo had a maze fad awhile back, we need to refad the mazes.
[img]http://puu.sh/1fFhS[/img] Is this happening to anyone else? Ignore the wordwrap error, that's my own.
use bit.band(...) instead of & and bit.bor(...) instead of | ... is vararg so like 1, 2, 3 etc
Well Garry switched to LuaJIT which also got rid of the bitwise operators.
[QUOTE=G4MB!T;38070297]use bit.band(...) instead of & and bit.bor(...) instead of | ... is vararg so like 1, 2, 3 etc[/QUOTE] Can't you just replace "|" with "or" and "&" with "and"? Or am I missing something? [editline]16th October 2012[/editline] Actually, if I read [url=http://wiki.garrysmod.com/page/Specific_Operators]this[/url] right you can replace them with "||" and "&&"
[QUOTE=highvoltage;38070328]Can't you just replace "|" with "or" and "&" with "and"? Or am I missing something? [editline]16th October 2012[/editline] Actually, if I read [url=http://wiki.garrysmod.com/page/Specific_Operators]this[/url] right you can replace them with "||" and "&&"[/QUOTE] bitwise or isn't the same as or.
Bitwise operators and normal operators are 2 different stories. [editline]16th October 2012[/editline] :ninja:
[QUOTE=vexx21322;38070456]bitwise or isn't the same as or.[/QUOTE] Just curious, but whats the difference?
[QUOTE=highvoltage;38070515]Just curious, but whats the difference?[/QUOTE] bitwise works on the individual bits. or is used in conditionals.
[QUOTE=vexx21322;38070567]bitwise works on the individual bits. or is used in conditionals.[/QUOTE] So I have been using them wrong all along? Good thing I only used "|" instead of "or" the odd time then.
[QUOTE=highvoltage;38070643]So I have been using them wrong all along? Good thing I only used "|" instead of "or" the odd time then.[/QUOTE] | is the bitwise or, or is the conditional operator.
[QUOTE=CapsAdmin;38060364]What do you find appealing about Moonscript? To me I feel like it's step down from Lua. I find it comparable to choosing between Lua or ms batch. I guess it's fun to setup and try? It looks well designed on the outside (didn't read its source) and I think it probably serves as a good example on how to make a new language with Lua.[/QUOTE] I honestly lost all appeal in Moonscript after a day of playing with it. It's based off of a modular system, a system that isn't compatible with Garry's Mod because Garry's Mod doesn't operate around modules, instead everything is held globally. The only reason I ever used Moonscript was because I fell in love with Coffeescript. Honestly, Lua is a step up from Coffeescript, and Moonscript is a step down from Lua. Moonscript also uses a binary module for it's lexing. Not all of it is in Lua, which is very unfortunate. Also, Moonscript files do not need to be in the same folder as the Moonscript compiler. If you have a basic command-line workflow set up and you add your Moonscript folder to PATH's, then you can just run "moonc" from a folder. Even better, you can set up a makefile.
[QUOTE=vercas;38059987][img]http://puu.sh/1fte6[/img] The code I used to test vAdmin's skin.[/QUOTE] :suicide:
[QUOTE=Nexus435;38063785]Seems you don't know what a core or a thread is. Because tokenizing strings needs 4 cores of processing power right? Sounds totally legit.[/QUOTE] Lemme xpwain how I do it. Core #1 (second core) tokenizes the string. Core #2 (third core) waits for the tokenizer to advance, and it keeps searching for strings and patterns and marks them. Core #3 (fourth core) awaits for marks and replaces them in the string and changing an offset (depending on what was replaced with what) so the tokenizer and the finder know not to check the same stuff again. (Or even misfire) Core #0 (first core) has the easiest job. First it processes some basic macros (in the input code), then it takes care of file I/O and starts up the other 3 routines. That is only the builder, but there's another program running, which watches the filesystem in a given directory (from core #0) for changes and renames, and adds everything to a Parallel Queue to be processed (in the right order) in the other cores (all of them). The builder is instant due to this, but the most important feature (for me) is the efficiency - [B]less time to produce heat[/B] - which burns the fuck out of my feet. When my files are 100 KB big or so, this actually makes a difference. I might even share it if you stop being asses about it.
It sounds like you should be sharing it with [url]http://thedailywtf.com[/url] rather than us, tbh
My gamemode i'm working on [IMG]http://cloud.steampowered.com/ugc/918992053262244354/41E58C1B1B0748FF6F8F3E8CD66A2FA2C2B9A8A5/[/IMG] [IMG]http://cloud-2.steampowered.com/ugc/918992053262254912/40199EEC0176EB1C1B4A20EDB5AACF3D82BFA0F1/[/IMG] sadly i can't work on it right now because mysqloo ain't working.
Vercas are you making an admin mod for Gmod 13? Because it looks really good!
[QUOTE=sarge997;38074387]Vercas are you making an admin mod for Gmod 13? Because it looks really good![/QUOTE] Yes, I'm making a new admin mod. I find the current admin mods flawed because they are too simple. They leave out useful features because they are either complicated to implement or complicated to understand. I'm making an admin mod for the more technical administrators (like Lua programmers). There's just so much to do... So much to take care of...
[QUOTE=vercas;38073476]Lemme xpwain how I do it. Core #1 (second core) tokenizes the string. Core #2 (third core) waits for the tokenizer to advance, and it keeps searching for strings and patterns and marks them. Core #3 (fourth core) awaits for marks and replaces them in the string and changing an offset (depending on what was replaced with what) so the tokenizer and the finder know not to check the same stuff again. (Or even misfire) Core #0 (first core) has the easiest job. First it processes some basic macros (in the input code), then it takes care of file I/O and starts up the other 3 routines. That is only the builder, but there's another program running, which watches the filesystem in a given directory (from core #0) for changes and renames, and adds everything to a Parallel Queue to be processed (in the right order) in the other cores (all of them). The builder is instant due to this, but the most important feature (for me) is the efficiency - [B]less time to produce heat[/B] - which burns the fuck out of my feet. When my files are 100 KB big or so, this actually makes a difference. I might even share it if you stop being asses about it.[/QUOTE] What's all this talk about 'cores'? It sounds more like you just made your little Moonscript [s]parser[/s] lexer have 4 main processing functions to handle the moonscript code itself, which I wouldn't exactly call a 'core' in this case.
[QUOTE=vercas;38074489]Yes, I'm making a new admin mod. I find the current admin mods flawed because they are too simple. They leave out useful features because they are either complicated to implement or complicated to understand. I'm making an admin mod for the more technical administrators (like Lua programmers). There's just so much to do... So much to take care of...[/QUOTE] I think quite the opposite, most current admin mods seem way overcomplicated to me.
Sorry, you need to Log In to post a reply to this thread.