Next line by Login!

[xCoCex]

ehh when I pressed # in the Log-In Room I get this:


not really important :D Whatever.
-coce :P

[foG]

I think this is a known bug, at least I found this one when SO was public and thought it was solved, apparently it wasn't.

[God-I-Suck]

lol it worked. XD

[Torch]

I would edit that picture so people can't see your password.

[xCoCex]

this is not my passwort lmao

[Scotty]

this is not my passwort lmao

But I guarantee someone is very disappointed right now thinking it was!

[JoEL]

Don't press # - Problem solved. No credit needed Meiun.

Encase anyone wants to know why this happens '#' is the symbol used to move text to a new line in game maker. Different languages have different methods for adding new lines to text, like C++ uses '\n'.

[krele]

Don't press # - Problem solved. No credit needed Meiun.

Encase anyone wants to know why this happens '#' is the symbol used to move text to a new line in game maker. Different languages have different methods for adding new lines to text, like C++ uses '\n'.

It wasn't solved at all by that... Perhaps some people use that character in their password? This is only a habit of bad coding... Worse than clicking on "Treat uninitialized vars as 0"...

There is an easy workaround though, replacing # with /# in a string works.

[Scotty]

Problem solved. No credit needed Meiun.

Well isn't that quite the sense of entitlement you hold there...

[JoEL]

Don't press # - Problem solved. No credit needed Meiun.

Encase anyone wants to know why this happens '#' is the symbol used to move text to a new line in game maker. Different languages have different methods for adding new lines to text, like C++ uses '\n'.

It wasn't solved at all by that... Perhaps some people use that character in their password? This is only a habit of bad coding... Worse than clicking on "Treat uninitialized vars as 0"...

There is an easy workaround though, replacing # with /# in a string works.

1) You can't use # in your name
2) It does solve the problem.

Problem solved. No credit needed Meiun.

Well isn't that quite the sense of entitlement you hold there...

Yes indeedy.

[Scotty]

Don't press # - Problem solved.

... So what you are saying, is that in order to avoid this "glitch" (for lack of better terms), you have to ask the community to please abide by a user-dependent workaround?

That's like saying, "In order to prevent users from maliciously altering the gaming experience of others, we ask that you please not 'crack' the game, although it is entirely possible for you do so if you feel like not listening to us.  Not like we could enforce you past being polite in asking..."

Holy crap, I wish your method was fool proof though.  Man would that take all the stress of security and flush it down the toilet!  I'm going to go ahead and do something I have never done, and am amazed that I'm doing it now.  I am going to go and agree with Krele for the first (and likely only time), in that if there are characters that, if not escaped, will throw exceptions, or result in these "glitches," being so naive to politely (or in your case, egotistically) ask the community to not do it is not enough.  These characters need to be escaped to prevent this error from occurring.

[JoEL]

Don't press # - Problem solved.

... So what you are saying, is that in order to avoid this "glitch" (for lack of better terms), you have to ask the community to please abide by a user-dependent workaround?

Yes exactly, finally someone understands! This is how the world should work.

[Aqua]

Not really... For good programming, I prefer to go to my expenses so that the players do not. At any rate, I assume that this will be fixed in the next version, and that this topic will be suddenly closed some time soon.
~Aqua

[Scotty]

Don't press # - Problem solved.

... So what you are saying, is that in order to avoid this "glitch" (for lack of better terms), you have to ask the community to please abide by a user-dependent workaround?

Yes exactly, finally someone understands! This is how the world should work.

And that right there is what makes you a piss-poor developer...

[krele]

Don't press # - Problem solved.

... So what you are saying, is that in order to avoid this "glitch" (for lack of better terms), you have to ask the community to please abide by a user-dependent workaround?

Yes exactly, finally someone understands! This is how the world should work.

And that right there is what makes you a piss-poor developer...

Thumbsup!