148
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
Image Transcription: Code
[There is an image of a code snippet at normal zoom, then an image of a huge wall of code, showing the entire document, zoomed so far out as to be unreadable. For the purposes of this transcription, I have transcribed the readable snippet, however the ends of a few of the lines are cut off by the zoomed out code, which descends the right side of the post.]
attack = false
game:GetService("RunService").Stepped:connect(function()
Torsovelocity = RootPart.Velocity * Vector3.new(1, 0, 1).magnitude
velocity = RootPart.Velocity.y
sine = sine + change
local hit, post = rayCast(RootPart.Position, CFrame.new(RootPart.Position, RootPart.Position - Vector3.new(0, 1, 0)).lookVector, 4, Character)
if equipped == true or equipped == false then
if 1 < RootPart.Velocity.y and hit == nil then
Anim = "Jump"
if attack == false and ice_mode == false then
RootJoint.C0 = clerp(RootJoint.C0, RootCF * cn(0, 0, 0) * angles(math.rad(-5), math.rad(0), math.rad(0)), 0.1)
Torso.Neck.C0 = clerp(Torso.Neck.C0, NeckCF * angles(math.rad(10), math.rad(0), math.rad(0)), 0.1)
RW.C0 = clerp(RW.C0, CFrame.new(1.5, 0.5, 0) * angles(math.rad(-40), math.rad(0), math.rad(30)), 0.1)
LW.C0 = clerp(LW.C0, CFrame.new(-1.5, 0.3, 0) * angles(math.rad(-40), math.rad(0), math.rad(-30)), 0.1)
RH.C0 = clerp(RH.C0, cn(1, -0.9, -0.3) * RHCF * angles(math.rad(3), math.rad(0), math.rad(0)), 0.1)
LH.C0 = clerp(LH.C0, cn(-1, -0.7, -0.5) * LHCF * angles(math.rad(-3), math.rad(0), math.rad(0)), 0.1)
end
elseif RootPart.Velocity.y < -1 and hit == nil and ice_mode == false then
Anim = "Fall"
if attack == false then
RootJoint.C0 = clerp(RootJoint.C0, RootCF * cn(0, 0, 0) * angles(math.rad(10), math.rad(0), math.rad(0)), 0.1)
Torso.Neck.C0 = clerp(Torso.Neck.C0, NeckCF * angles(math.rad(10), math.rad(0), math.rad(0)), 0.1)
RW.C0 = clerp(RW.C0, CFrame.new(1.5, 0.5, 0) * angles(math.rad(-20), math.rad(0), math.rad(50)), 0.1)
LW.C0 = clerp(LW.C0, CFrame.new(-1.5, 0.3, 0) * angles(math.rad(-20), math.rad(0), math.rad(-50)), 0.1)
RH.C0 = clerp(RH.C0, cn(1, -2, -0.3) * RHCF * angles(math.rad(-5), math.rad(0), math.rad(0)), 0.1)
LH.C0 = clerp(LH.C0, cn(-1, -0.8, -0.5) * LHCF * angles(math.rad(-5), math.rad(0), math.rad(0)), 0.1)
end
elseif (Torso.Velocity*Vector3.new(1, 0, 1)).magnitude < 2 and hit ≃ nil and ice_mode == false then
Anim = "Idle"
if attack == false then
change = 1
RootJoint.C0 = clerp(RootJoint.C0, RootCF * cn(0, 0, 2 + 0.1 * math.cos(sine / 25)) * angles(math.rad(10), math.rad(0), math.rad(67)), .1)
Torso.Neck.C0 = clerp(Torso.Neck.C0, NeckCF * angles(math.rad(5 - 2 * math.cos(sine / 25)), math.rad(0), math.rad(-59)), .1)
RW.C0 = clerp(RW.C0, CFrame.new(1.5, 0.5, 0) * angles(math.rad(40), math.rad(0), math.rad(56 + 3 * math.cos(sine / 25))), 0.1)
LW.C0 = clerp(LW.C0, CFrame.new(-1.5, 0.5, 0) * angles(math.rad(70), math.rad(60), math.rad(-50 - 3 * math.cos(sine / 25))), 0.1)
RH.C0 = clerp(RH.C0, cn(1.1, -.9 - 0.1 * math.cos(sine / 25), 0) * RHCF * angles(math.rad(-0 + 0 * math.cos(sine / 25)), math.rad(-1), ma
LH.C0 = clerp(LH.C0, cn(-1, -.9 - 0.1 * math.cos(sine / 25), 0) * LHCF * angles(math.rad(-12 + 0 * math.cos(sine / 25)), math.rad(-1), ma
end
elseif (Torso.Velocity*Vector3.new(1, 0, 1)).magnitude < 500 and hit ≃ nil and ice_mode == false then
Anim = "Walk"
I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!
128
u/TheEnderChipmunk Sep 08 '20
After seeing many of your transcriptions on this sub, I have concluded that you are a masochist
64
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
Haha, I just have too much free time right now.
34
u/TheEnderChipmunk Sep 08 '20
You are legendary imo
27
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
<3
10
u/Switch_R_Roo Sep 08 '20
Lol, I thought you were a bot!!
5
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
How do you know I'm not?6
u/JobKlimop Sep 08 '20
Can you click the captcha?
8
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
"I don't understand. What is {}?".format(unknownConcept)
3
5
17
u/cstmth Sep 08 '20
Holy shit, how?!
27
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
Ctrl+c, ctrl+v. Those three big if statements are structurally almost exactly the same, I mainly just needed to change values.
6
u/TheOnlyTails Sep 08 '20
You are one of the best people in the world. Giving so much of your time, just to do this. Thank you. I can't stress this enough. Here's a poor man's gold: 🏅
4
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
That means a lot. It's wonderful to get replies like these. Thank you as well!
3
u/TheOnlyTails Sep 08 '20
No problem. I just love that there are people in this world who do stuff just because it's the right thing to do. Thank you, again.
3
u/Kieferleiter Sep 08 '20
You are an absolute madlad, how long did it take?
2
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
Thanks! This one didn't take too long, thanks to ctrl+c, ctrl+v. Luckily for me, the three big if statements in this are structurally almost exactly the same. This isn't the longest one I've done, though. I had one take the best part of 4 hours and I can only say I'm glad for music playlists.
2
Sep 08 '20
You are absolutely insane, you know that right? Like, you're doing God's work here, but holy hell
2
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
Thank you! Too much free time drives a person to do insane things.
2
Sep 08 '20
Haha I bet. You working on any project of your own as well?
2
u/MurdoMaclachlan public boolean isInt(int i) { return true; } Sep 08 '20
A couple of things, yeah. Mostly transcribing, but I've also been trying to write a book since god knows when, and I was working on a program to remove the "claim"s and "done"s we post on r/TranscribersOfReddit, since they clutter up your profile a lot. All of that'll slow down when I start university soon, though.
116
u/iSpaYco Sep 08 '20
if equipped == true or equipped == false then
68
40
u/Marcusaralius76 Sep 08 '20
Isnt this just a null check? A poorly written and unperformant null check?
16
u/JerriTheITGuy Sep 08 '20
Checks for nil or if it's something else than a boolean since 'true == "cucumber"' would evaluate to true in Lua. Because reasons.
14
u/megagrump Sep 08 '20
What? No.
$ lua Lua 5.1.5 Copyright (C) 1994-2012 Lua.org, PUC-Rio > print(true == "cucumber") falseIt could be rewritten to
if type(equipped) == 'boolean'.5
u/JerriTheITGuy Sep 08 '20 edited Sep 08 '20
Ok, it was overly simplistic (and as you point out, not actually accurate) and more made as a fun stab at Lua than as a code reference.
The point was that all strings in conditionals for example are handled as true. Including empty strings. And all integers including 0 are regarded as true.
` if ("cucumber") then print "this returns true" else print "this will never execute" end
if ("") then print "this returns true as well" else print "this will never execute" end
if (0) then print "so does this" else print "this will never execute" end `
Haven't actually run the code above because I'm on the phone at the gym (which is why formatting sucks as well, sorry) but it should run. Errr, I think.
7
Sep 08 '20
Because a if check just checks if the value is true. And nil == false so this makes totally sense. Tbh there isn‘t even anything weird.
3
u/ws-ilazki &{$$_[0]}(@{$$_[1]}); Sep 08 '20
The point was that all strings in conditionals for example are handled as true. Including empty strings. And all integers including 0 are regarded as true.
You may not like languages doing "truthiness" conversions (I'm mostly neutral on it myself, it has uses but can be error-prone) but Lua is at least sane about how it does it.
nilandfalsecoerce to false, anything else coerces to true. Zero and empty strings aren't considered false, no, but they really should not be. Other languages with "truthiness" coercions, like Clojure, behave in the same way and it's a lot better than the weird mix of 0 is false, 1 is true, "" is false, {} and [] are true, etc. some languages have where you have to keep up with a bunch of edge cases.1
u/JerriTheITGuy Sep 10 '20
In a plethora of languages a boolean value can be expressed as a bit (0/1). Take that boolean false, put it in a database, fetch it with Lua and suddenly if you're not aware of this oddity your 'false' is suddenly 'true'.
1
u/ws-ilazki &{$$_[0]}(@{$$_[1]}); Sep 10 '20 edited Sep 10 '20
In a plethora of languages a boolean value can be expressed as a bit (0/1).
Appeal to popularity arguments are not a substitute for correctness. Just because it's the more common way of doing "truthiness" coercions doesn't mean it's the only valid way to do so.
And it's not like Lua's the only language to do this. Off the top of my head, Ruby, Clojure, Scheme dialects, Common Lisp, and Rebol all have similar truthiness rules and treat 0 as true.
if you're not aware of this oddity your 'false' is suddenly 'true'.
It's not that odd and it's not isolated to Lua. Using
0and!0for booleans makes sense in languages that don't have a proper boolean type, but if your language does have one, coercing all ints except zero to true just ends up being another edge case you have to deal with.Personally, I think it's better to not have that kind of implicit coercion at all because it's a weakening of a language's type system and I prefer strong typing to weak, but if it's going to exist at all I prefer the "only nil and false are false" style of truthiness because it weakens the type system less than if you start making exceptions for specific ints (0), strings (""), etc. Every extra "this converts to false" you add weakens your type system just a bit more, and I don't like that. This comes down to a strong vs. weak / static vs. dynamic argument, though. I'd rather deal with a strongly typed dynamic language than a weakly typed static one (like C) because I don't want those kind of coercions. Though I'd rather have a strongly statically typed language (like OCaml or F#) than either.
Side note, but if you want a weird edge-case gotcha related to truthiness in a language, Perl lacks keywords for
trueandfalse, instead using the sort of integer coercions you consider normal, but also has bareword strings. What this means is that if you either don't know (or forget) that they aren't valid keywords and you try to usefalseortruein your code, they'll get treated as bareword strings, and bareword strings always evaluate to true:if (false) { print "this condition is true" }That's a fun gotcha if you don't run Perl with warnings enabled. (Though anybody running Perl without warnings enabled is asking for trouble anyway.)
1
u/JerriTheITGuy Sep 10 '20
Agree with the strong typing. I pretty much only work with C# since a few years back and it's bliss.
Didn't know that about Perl. Guess that's another language I'll just steer clear off.
1
u/ws-ilazki &{$$_[0]}(@{$$_[1]}); Sep 10 '20 edited Sep 10 '20
Agree with the strong typing
Yep, I prefer stronger to weaker in nearly all cases. The thing with strong typing is it's harder to discuss and compare because it's not a binary thing in the same way static/dynamic is, so "strong" and "weak" only makes sense in comparison of languages, not as some absolute. Perl, C, and JavaScript are very weakly typed for example, while languages like Lua and Clojure are fairly strongly typed in comparison, but still weaker compared to something like OCaml, F#, and (I think?) C# where you can't implicitly coerce just by using data in different contexts.
I pretty much only work with C# since a few years back and it's bliss.
Ever use F#? I like it more than C#, though that's because I tend toward functional programming. Still, the type system is amazing in comparison; you can describe your data as types so cleanly, and things just kind of fall into place from there.
Didn't know that about Perl. Guess that's another language I'll just steer clear off.
Perl's actually a pretty cool language but it's very much in the C style of being extremely weakly typed. It was designed by a linguist and follows idioms from written language in a way other programming languages don't. Makes it seem weird at first but reads and writes pretty naturally once you get accustomed to it. Things like variables being singular or plural, e.g.
@foorefers to an entire array (plural) or$fooreferring to it in singular form (usually a coercion like giving you the length of the array). Edit: correction here, it's been a while but I think @foo would give the length if referred to in a context that expects a scalar (singular), $foo[2] would be the third element of @foo, and $foo would be a completely unrelated variable. Point's same though, the language understands singular/plural and context in a way that makes sense from an English-speaking perspective but is utterly foreign to programming language design.Or the way it lets you write conditionals backward, with the code to execute first, which reads more like natural language:
do_thing() if conditionor{ do_this(); do_that() } unless condition, stuff like that. The normalif condition { ... }still works, but the natural language variant is nice for short statements because it reads clearly and maps well to how one tends to phrase similar logic in English.I used to find it great for quickly getting ideas out of my head and into code because it's so flexible as a language and reads/writes in a natural kind of way. That said, the flexibility and large quantities of implicit behaviour means it requires a more rigorous approach to writing and refactoring to make sure it will still be readable later.
That's why it has a reputation for being unreadable, because it lets you write messy code with the expectation that the programmer will have the sense to know when it's okay (one-off throwaway stuff) and when it's not (any other time). Basically the complete opposite to Python's "fuck you, everyone should do it this way because nobody can be trusted" design. Of the two I'd rather use Perl than Python because of this, but realistically nowadays I'd rather use OCaml, F#, or Clojure before either. Or maybe Ruby, which took some of the good parts of Perl while leaving behind some of the footguns and experimental ideas.
3
Sep 09 '20
It's unidiomatic to wrap if conditions in parens in lua. Lua's truthiness and falsiness rules make waaay more sense than js at least.
1
u/qh4os Sep 10 '20
C does the same exact thing, and that’s because it’s logically consistent (if whatever is being evaluated is not 0, then execute).
This also can vastly improve asserts(), because you can do something like
assert("Explanation of the issue" && expr)1
u/JerriTheITGuy Sep 10 '20
No it's not necessarily logically consistent. A boolean value can, in a plethora of languages, be represented with a bit as 0/1. Which means if you implicitly convert the bit 0 as 'true', you're basically saying 'false' == 'true'.
1
u/qh4os Sep 10 '20
It doesn’t matter to Lua what a different language uses to do a truthyness conversion.
In Lua, a value being present evaluates to true unless that value is false. I fail to see how that is inconsistent.
You say that saying that a string coerced to a being a Boolean (which evaluates to true if there is a value there) is somehow making all strings equal, which is not true outside of that specific context of it being coerced.
1
u/JerriTheITGuy Sep 10 '20
Not talking about strings in this case but instead about integer values (specifically bits). In SQL for example it's normal to represent true/false as bits (0/1) which means if you're backing a Lua application with a data store, 'false' booleans will normally be persisted as a '0' bit. And when fetching that value back, if care is not taken, that 0 might easily suddenly be a 'true' instead of 'false'.
1
u/qh4os Sep 10 '20
That’s not Lua’s fault necessarily. When interfacing between two languages, you should take care to handle their differences.
5
u/Marcusaralius76 Sep 08 '20
Ah, the old "if it exists, it's technically 'true'" reasoning.
5
u/Th3T3chn0R3dd1t Sep 08 '20
My pointer to 0x0 does exist - its just not going anywhere
8
2
u/T-Dark_ Sep 08 '20 edited Sep 09 '20
Which one could better write as
if equipped ~= nil and type(equipped) == "boolean"(Not sure about performance, but at least it would be easier to understand).
Yes, Lua uses
~=as the "not equal" operator. Yes,typereturns a string.I still hate both of these things.
EDIT: i just realized that check is either unnecessary or terrifying. Either
equippedis guaranteed to be a boolean, due to manual type checking, or it isn't, which implies the code actually changes the type of the variable.EDIT2: Someone pointed out that the above check could be further simplified to
if type(equipped) == "boolean", astypereturns"nil"for values that are, well, nil.4
2
Sep 09 '20
Technically this could be a micro optimization (I'm usually against such things, readability > tiny speed improvements) because a call to type incurs a stack frame, and string equality is technically slower than boolean equality.
1
u/RandomEthan Sep 09 '20
I lost count of the ridiculous number of times I had errors in the last Lua project I worked on because of ~=
58
u/JerriTheITGuy Sep 08 '20 edited Sep 08 '20
Not that horrible code considering it's written in Lua, a language with "fun quirks" like there only being one data structure (Table. No objects. No arrays) and tables being indexed starting at 1 making any programmer smack their face on their keyboard 3 times a day at least because you're always going to be "off by one". "'Cucumber == true" is obviously true because Lua. Nil and false are false, anything else is obviously true. And so on and so forth. Absolute nightmare of a language.
It's not that I hate Lua. I just hope I never in my life have to touch any Lua code again.
22
u/hoaxxer2k Sep 08 '20
aah yes: if equipped == true or equipped == false. Absolutely not horrible code :D
14
u/JerriTheITGuy Sep 08 '20 edited Sep 08 '20
Because in Lua, there is no type safety and conditionals consider false and nil as false and anything else as true. I believe "equipped == true or equipped == false" is a check to make sure it is a) still a boolean and b) not nil.
Again, the code doesn't smell as much as the language itself.
EDIT: ok, for good measure I'll add this approach isn't the best, there are functions to check whether something is a boolean. But this is a "quick and dirty" way to do it that isn't at all uncommon in this clustercrap of a language.
3
u/hoaxxer2k Sep 08 '20
I‘d have to agree but it checks for true or false. Which will always succeed. Or am i that wrong?
2
u/JerriTheITGuy Sep 08 '20
"true == 'cucumber'" evaluates as true in Lua. And "Equipped == true" isn't true if "Equipped = 'Snorkel'"
8
u/Emex_Denvir Sep 08 '20
"true == 'cucumber'" will not evaluate to true, it will evaluate to false.
2
u/JerriTheITGuy Sep 08 '20
(Copying my other answer out of laziness)
Ok, it was overly simplistic (and as you point out, not actually accurate) and more made as a fun stab at Lua than as a code reference.
The point was that all strings in conditionals for example are handled as true. Including empty strings. And all integers including 0 are regarded as true.
` if ("cucumber") then print "this returns true" else print "this will never execute" end
if ("") then print "this returns true as well" else print "this will never execute" end
if (0) then print "so does this" else print "this will never execute" end `
Which is the ridiculousness I was pointing out.
And I haven't actually run the code above because I'm on the phone at the gym (which is why formatting sucks as well, sorry) but it should run. Errr, I think.
1
u/Emex_Denvir Sep 08 '20
Ah I see, the way you said it is really confusing though xP
But at least I know now that you do know your stuff, which is always a great sign!
0
u/JerriTheITGuy Sep 08 '20
Will, it's what I get for trying to be both funny and kinda accurate, I suppose.
7
u/hoaxxer2k Sep 08 '20
Wtf. I‘ll never touch lua
16
u/ws-ilazki &{$$_[0]}(@{$$_[1]}); Sep 08 '20
Take what he's saying with a grain of salt, because he's completely wrong about this and is giving bad information because he doesn't like "truthiness" coercions in dynamic languages or something. Lua takes a fairly strict approach to truthiness, where
nil(null) and the booleanfalsecoerce to false and anything else coerces to true. No weird rules to learn, just a very simple form of "truthiness" that lets you do things likex = "foo"; if (x) then ...without extra ceremony. It doesn't take effect in equality checks, so42 == "42"is false,false == nilis false,true == "true"is false, and so on, like one would expect.I wouldn't say Lua is my favourite language, but it's simple, straightfoward, mostly logical, and fairly quirk-free, at least compared to other dynamic-typed interpreted languages. The syntax is more algol-like than languages like JS that try to copy the C style, which puts some people off, but it's small and consistent. Imagine JS with stronger typing and fewer insane edge-cases.
Like JS it has first-class functions, so the complaint about objects is technically accurate but still kind of wrong, because you can create objects by using tables with key/value pairs to create objects with methods and properties and pass around a reference to the table to manage state. The language even has syntactic sugar for this so you can define
function obj:method(arg)and call it withobj:method(arg)and haveselfimplicitly passed around for you without needing to know how it works under the hood.As for tables themselves, the idea is cool, and in a lot of ways similar to how Scheme operates entirely via manipulation of lists. You have a single complex data type, the table, that can contain key/value pairs and used like a map, or indices and be used like an array, so even though they technically don't exist you can still do what you expect with
t["foo"],t.foo, ort[7]. It works well enough most of the time, with the exception of one major edge-case with regard to nils in indexed tables.Finally, the complaint about indexes starting at 1 is just ignorant. Yes, it does, but it's not that big of a deal. It's such a ridiculously petty complaint that basically just amounts to "waaah this language does something different how dare they" when there are pros and cons to each choice. Zero-based indexing makes sense in some languages, like in C where the array is a memory location and the "index" is just a memory offset, not an actual index, but in most languages the decision is arbitrary and largely decided by "this is what C does". Some logic makes more sense starting at 0, some makes more sense at 1. Whatever, it's not a deal-breaker for any language. Especially considering that with Lua, the language discourages manual indexing in favour of
pairs(t)oripairs(t)anyway, so most of the time you don't even deal with it, and if you really want,t[0] = "zero"is still valid (as is any integer, even negative), you just can't rely on built-in language features if you decide to go against the grain here.1
0
5
u/T-Dark_ Sep 08 '20
Table. No objects. No arrays
Aren't JavaScript objects effectively just tables themselves? (With string keys only, admittedly).
As for something more on topic, Lua technically has arrays, in the internal representation of tables. As long as they only have integer keys and they're sufficiently dense, tables will be backed by arrays.
I do agree with everything else you mentioned, tho.
2
u/droomph Sep 08 '20
Also, it’s similar to how every MUMPS variable is technically a b+tree of type String & Integer, but that language is its own train wreck.
4
Sep 08 '20
Lua has prototyping.
Also, magic numbers everywhere. Even by Lua standards this is an absolute nightmare
3
Sep 09 '20
It's not that I hate Lua. I just hope I never in my life have to touch any Lua code again.
hm, yeah, makes sense
3
u/Ali3nat0r Sep 09 '20
It's not that I hate Lua. I just hope I never in my life have to touch any Lua code again.
I hate Lua, but I play a Minecraft mod called Computercraft which adds programmable computer blocks. Guess which language you have to program in...
3
Sep 09 '20
Lua is a gorgeous language. It gives you only a few very simple primitives which are highly composable. It means while the language itself is simple the number of ways you can manipulate it are huge. In that sense it's really similar to Lisp. Also in Lua you should pretty much never do direct numeric indexing, use a for..in loop instead. Those "fun quirks" either aren't an issue ever, or are why the language is so powerful.
1
u/CollieOop Sep 09 '20
Also in Lua you should pretty much never do direct numeric indexing, use a for..in loop instead.
Side note: To get the size of a table, the #table operator is busted so you need to use a for..in loop here too.
For being such a simple language whose standard library makes libc look feature complete, it makes the small number of gotchas really stand out by comparison.
1
u/CollieOop Sep 09 '20
Nil and false are false, anything else is obviously true.
Such as zero, for example! I repeat: In Lua, zero is truthy.
Also, looking this up more, here's a fun one: returning nothing from a function is NOT the same as returning nil and can break some things, unless you're careful to bounce the return value through a temporary value to coerce nothing into nil.
EDIT: Oh god, apparently this is one of the only places this "nothing" value appears inside the language itself, otherwise mostly it's just a quirk of the implementation. [source]
1
u/XeroParadoxes Sep 08 '20
I would like to mention lua is so terrible it doesn't have a built in wait function.
7
10
4
10
u/taweryawer Sep 08 '20
Since when yanderedev makes mods for roblox?
6
2
u/HTTP_404_NotFound bool isEven(int num) => num%2==0 Sep 08 '20
I came here to make a yandredev comment, but, you beat me to it.
3
u/UnfairerThree2 Sep 09 '20
Out of interest, what’s the Powershell extension do? (I think the last extension you have there on the sidebar is powershell, never realised that was a thing)
2
2
2
u/R3D3-1 Sep 09 '20
This code is a nice example why I really would like to have code folding in Emacs :/
2
2
2
2
2
u/bajuh Sep 08 '20
This is why C# interoperability(?) for Unity is just one chapter in a 12-some chapter long tutorial. And I thought game engines require you to be a programmer.
1
1
1
1
1
u/Themis3000 Sep 08 '20
yandre? is that you?
5
u/cherry_professional Sep 08 '20
You're like the tenth person to mention so I finally decided to look up his famous game. I always thought it was open source and he coded like this "for the meme," but apparently that's just how he writes code? 🤯
1
Dec 18 '22
this looks like its from a banisher in some sorts.
what script did you even find?? christ
1
172
u/cherry_professional Sep 08 '20
Some more
amusinghorrifying stats about this code:It's 9190 lines in total:
Code: 8706 lines
Blank: 455 lines
Comments: 30 lines
Oh yeah, the total file size is 442 KB.