Main Menu
Main Page
Forums
Recent changes
Random page
Help

Databases
GlitchDex
AttackDex
ItemDex

Major Glitches
Trainer escape glitch
Old man trick
Celebi trick
Select glitches (Japan)
SRAM glitch
CoolTrainer♀ corruption
LOL glitch
Rival LOL glitch
Super Glitch
ZZAZZ glitch
Pomeg corruption glitch (Glitzer Popping)
Tweaking
Elite Four door glitch (Japan)
Pokémon merge glitch
Pokémon cloning
Time Capsule exploit
Arbitrary code execution
Coin Case glitch
More

Other Glitch Categories
Glitches by generation
Glitches between two generations
Japan-only/language specific glitches
Music glitches
Natural glitches
Non-core series glitches
Non-Pokémon glitches
Officially acknowledged glitches
Recurring glitches
Dead glitches

References
Pokémon GameShark codes
The Big HEX List
GB programming
Curiosities
Debugging features
Easter eggs
Error traps
Glitch areas
Glitch myths
Non-glitch exploits
Placeholder texts
Pokémon glitch terminology
Unused content and prerelease information

Useful Tools
8F Helper
GBz80 to Items
Old man trick name generator
PATH (Prama's Advanced Tweaking Heaven)
Save file editors
Special stat/Pokémon converter
Trainer escape Trainer Pokémon finder

Affiliates
Legendary Star Blob 2 (Hakuda)
Pokémon Speedruns wiki
PRAMA Initiative
Become an affiliate!

Search Wiki

 

Search Forums

 

Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture Type the letters shown in the picture Type the letters shown in the picture Type the letters shown in the picture Type the letters shown in the picture Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
(Use numbers) In G/S/C, how many Pokémon hexes hold glitch Pokémon? (the BIG HEX LIST can be used) Hint:  ????? and EGG are glitch Pokémon (http://glitchcity.info/biglist.htm):
(http://glitchcity.info/wiki) Unlike every other MissingNo, can the NON-SKELETAL/GHOST, YELLOW Version MissingNo crash your game after encountering it? (yes or no):

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Calhaora
« on: October 15, 2016, 03:28:12 pm »

Hooray, finally I can ask dumb questions again ^-^
Posted by: Missing? NO!
« on: October 08, 2016, 11:33:44 pm »

Posts seem to go through a lot faster and everything runs smoother as a whole. Glad it's back!
Posted by: SatoMew
« on: September 19, 2016, 04:24:45 pm »

I hadn't come here in a while but I'm glad the migration went fine! :)
Posted by: Charmy
« on: August 15, 2016, 01:08:01 pm »

I was looking almost every day to see if the maintenance has finished.
However, there's one problem.
The Forum Rules page is dead, and new users will not obey the rules more often, because they can't access the page.
Posted by: Bert
« on: August 09, 2016, 02:40:41 pm »

Yay, I get to annoy people again!
Posted by: Torchickens
« on: August 09, 2016, 01:31:59 pm »

Eventually the extension will be dropped and replaced with something better, but for now I wanted to fix it up so it works properly again. Some of the entries have been hand-converted into proper pages or formatted, and the "back to the index" link confuses the parser into thinking that's the name of the Pokémon/item/attack since the parser expects the first line to be the name. Removing that should update the name shown on the index (that's the intention)... but no guarantees, as the extension is not as "super awesome" as it claims to be!

The new extension will use MediaWiki's template syntax which will more easily allow for things like wikilinks and images. The intention will be to keep the things the extension brings like separation of markup from data, and the ability to sort and (eventually...) filter the index, while being allowed to freely use native wiki code.
That sounds neat, looking forward to it! :)

Yeah, I tried to remove back to index link and replaced the first two lines with "[new line][item name]" but the index is still showing "([[ItemDex|↑ Back to the ItemDex index]].) with (0) in the ID field and 0 in the price field for me.
Posted by: drc
« on: August 09, 2016, 01:26:30 pm »

yay ;D
Posted by: Abwayax
« on: August 09, 2016, 12:35:52 pm »

Eventually the extension will be dropped and replaced with something better, but for now I wanted to fix it up so it works properly again. Some of the entries have been hand-converted into proper pages or formatted, and the "back to the index" link confuses the parser into thinking that's the name of the Pokémon/item/attack since the parser expects the first line to be the name. Removing that should update the name shown on the index (that's the intention)... but no guarantees, as the extension is not as "super awesome" as it claims to be!

The new extension will use MediaWiki's template syntax which will more easily allow for things like wikilinks and images. The intention will be to keep the things the extension brings like separation of markup from data, and the ability to sort and (eventually...) filter the index, while being allowed to freely use native wiki code.
Posted by: Torchickens
« on: August 09, 2016, 09:08:46 am »

Great we're back! :)

I understand you're busy but have a couple of questions and a suggestion, you know how the GlitchDex and ItemDex have a "([[ItemDex|↑ Back to the ItemDex index]].)" option? I modified the pages to have this when the extension wasn't working and have now made them pages like the other database entries, but the contents pages still say this.

1) Will the entries for the names of things on the GlitchDex, AttackDex and ItemDex eventually update or do you have to update them by another means?

2) Is it possible to add links and images on the database entries (like RB:191 could link to Trainer escape glitch, or glitch Pokémon front sprites and backsprites)?

Suggestion: Can you add a criteria for Time Capsule Exploit/Johto guard glitch learned moves please?

Thanks!
Posted by: Wack0
« on: August 09, 2016, 08:37:21 am »

And here I was, scared about the prospect of another long downtime over 1 year :)
Posted by: LanceAndMissingNo.
« on: August 09, 2016, 08:29:35 am »

I hope that new changes make the forums becomes better, regards!  ;)
Posted by: Krys3000
« on: August 09, 2016, 07:19:50 am »

Great! I was getting bored to come everyday check if it was back  :P
Posted by: Abwayax
« on: August 09, 2016, 01:39:24 am »

It took longer than I wanted to, but we are finally back online.

Along with the server migration, some infrastructure changes were made which should make the site run better and also make it easier to develop. These were changes I had been wanting to make for a while and figured with the server migration this was a perfect time to leave the legacy infrastructure behind and start anew.

Updates made:
- MediaWiki updated to 1.27. This necessitated a lot of changes to some of the extensions and the skin (we really haven't been doing updates as often as we should...)
- SMF updated to 2.0.11. The existing SMF codebase has been wiped, sans themes. Any mods that were installed on the old one will be re-installed, and then integrated into the codebase.
- -Dex extension ("Professor Glitch's Super Awesome Extension") fixed up so it renders things properly.

Technical changes:
- GCL now runs as a self-contained web application inside a Docker container, using php5-fpm + nginx. The front-end webserver runs nginx proxying into this application. All of the code for this application is available on our self-hosted GitLab instance at https://gitlab.monarch-pass.net/glitch-city-laboratories/glitch-city-laboratories.
-- Previously the front-end server was an Apache instance which ran GCL and some other sites under mod_php.

The other bugs which are known about have still not been fixed yet, but I wanted to get this version of GCL back online before tackling them. This setup allows me to have a development environment where changes can be made and tested before being pushed to production.