Main Page

Today I'm announcing the official opening of the Glitch City Laboratories IRC chatroom, #glitchcity.

Click here to go to the web chat interface or set up your chat client to connect to #glitchcity on irc.eightzees.net.

This chatroom is governed by the same set of rules that GCLF is. As the official channel of the site, it is exempt from the "what happens in IRC stays in IRC" rule usually enforced for third-party channels such as #zanzibar.

BASIC IRC COMMANDS
(text in <brackets> is a placeholder. The word "channel" means chatroom)

* /join <channel> joins a channel. If the channel does not exist, it is created
* /part leaves the current channel.
* /quit disconnects from the server.
* /me <text> creates "action text" that might look something like this: " * malacoda <text>".
* /msg <user> sends a private chat message to another user. It is used to start private conversations.

NICKNAME COMMANDS

* /nick <nickname> changes your nickname. If the nickname you want is registered by someone else, you will be informed.
* /msg nickserv register <password> registers your nickname with NickServ, the nickname service. Registration with NickServ is optional unless you are in a position of authority on the channel: registration is required to configure ChanServ (the channel service) to grant you any form of authority. Registration also allows you to reserve a nickname as your own and prevent others from taking it.
* /msg nickserv identify <password> identifies your current nick to NickServ. This is like "logging in". If you connect using a registered nickname, NickServ will prompt you to "identify".
* /msg nickserv ghost <username> <password> disconnects another user who is using your nickname. This is also useful if you disconnect but your nick remains connected to the server (as a "ghost" user).

USING THE WEB INTERFACE
When you load the web applet, some security related dialogs will appear.

* If you see a dialog saying Do you want to run this application? click RUN. You may also check the Always trust content from this publisher to prevent this dialog from appearing in the future.
* If you see a dialog saying Block potentially unsafe components from being run? click NO. If you click Yes, the applet will not run properly.

In an attempt to deal with the downtimes, my server's going to be upgraded sometime this week. Due to this, there will be some outage sometime within the next two days.

As of today, March 28, the Glitch City Laboratories Wiki is open to the public.

It wasn't closed, really, but now we've replaced the old site with it.

Most pages from the main site have already been transported to the wiki and rewritten. Mainly, what remains are the 'Dexes. However, one major part of the site in need of reformatting is the Gameshark codes page. Creating the page in a comprehensive and organized format will take a long time with the insane amount of codes, so why not help out? It'll be an easy way to get involved. Simply follow the format already introduced here: http://glitchcity.info/wiki/index.php?title=Pok%C3%A9mon_GameShark_Codes_(Generation_I)&stable=0
and add more codes from the makeshift page here:
http://www.glitchcity.info/wiki/index.php/Pokemon_Red,_Blue_and_Yellow_Gameshark_Codes
Any values that don't seem to have been documented, or any codes that don't seem to have a known effect? Test them out, and add your findings. This'll be a long project, so if you feel like helping, please do!

Happy New Year! 2009 was an excellent year but we're hoping 2010 will be even better.

Now, as for the outage yesterday. Our host SystemInPlace did some maintenance today, which included a switch to another internet provider. As a result, the IP of the VPS was changed and I had to renumber some network configuration accordingly. I apologize for the inconvenience.

The email sent by SystemInPlace:

Hello,

We will be performing many software updates and also reorganizing our
hardware in our cabinets today, as well as taking the final steps to
ween ourselves off of the HE circuit which will be unavailable as of
January 11th.

A reminder if you have not renumbered your VPSes:

- 64.71.161.x IPs are now 69.162.132.x IPs.
- 66.160.197.x IPs are now 69.162.133.x IPs.
- 216.66.9.x IPs are now 69.162.134.x IPs.

IPv6 is now up and running on the Steadfast circuit, if you have not
done so, change the 2001:470:3 prefix in your address to the
2607:f128:42 prefix.  Open a ticket if you need RDNS delegation.

After today, VPS and gameservers will no longer have HE IPv4/IPv6
transit available to them, as we will be directing the circuit into one
specific machine to continue to host our resolvers on for the time
being.  So if you have not renumbered your VPSes, you need to do that
*now*.

The SystemInPlace team wishes you a happy and safe 2010, and looks
forward to doing business with you for the oncoming year.