Anonymous user
Talk:DecDex/Data (Ruby/Sapphire): Difference between revisions
no edit summary
>Bwill11 No edit summary |
>Sherkel No edit summary |
||
Line 3:
:I would just use a table to organize things. HTML itself doesn't really support multiple spaces in a row. [[User:Bbbbbbbbba|Bbbbbbbbba]] ([[User talk:Bbbbbbbbba|talk]]) 18:36, 23 August 2019 (-06)
:Incidentally, I want to ask you a question: Why do you want to complete the GlitchDex? That is (roughly), what do you use the GlitchDex for? I think the answer to this question would give me some insight on how to reorganize the wiki. [[User:Bbbbbbbbba|Bbbbbbbbba]] ([[User talk:Bbbbbbbbba|talk]]) 13:51, 26 August 2019 (-06)
::I've been completing the GlitchDex primarily out of boredom. I think it's interesting, and since my summer vacation is completely vacant, I decided that it would be a good way to fill that void. I picked the GlitchDex specifically because I currently have no access to debugging features (I don't have a working PC at the moment, just the school Chromebook that I'm typing this on, so since I can't run bgb, I have to go with mobile emulators), so I can't figure out things like specific effect pointers on glitch items. I've mostly done the GlitchDexES because I've been learning Spanish and like to play video games in Spanish over the summer so I don't forget everything I learned the previous year. (Obviously I don't end up using most of what I learned in class in the game, but just more exposure to the language helps, especially compared to the nothing I'd otherwise be doing) I've cleaned up and filled out some of the DecDex just because there's nothing else to do. --Bwill11 06:43, 27 August 2019 (-06)▼
:::Personally I'm no proponent of the DecDex, as any exploits related to them will be found through finding which attack animations point to RAM, not going through and taking a brief glance at each of the hundreds of thousands of values one can modify the enemy species to. I would say the most important of the database projects are the ItemDex and MetascriptDex for the usefulness they've already demonstrated (I could be missing some). I relate heavily to the curiosity factor bwill11 mentioned, being around when this site was just getting started and lurking on earlier ones during formative years, in addition to the fact they're simply impressive compilations of info. A new framework for organization should be based on priority, I think, though at the same time I don't want to impulsively toss the GlitchDex and AttackDex to the side considering the gateways and early examples they were...I don't really have it in me at the moment to give this site my full focus, but I think this discussion is important and will get back to it when I can, and would also like for however many others to pitch in as possible. [[User:Sherkel|Sherkel]] ([[User talk:Sherkel|talk]]) 10:09, 27 August 2019 (-06)
▲I've been completing the GlitchDex primarily out of boredom. I think it's interesting, and since my summer vacation is completely vacant, I decided that it would be a good way to fill that void. I picked the GlitchDex specifically because I currently have no access to debugging features (I don't have a working PC at the moment, just the school Chromebook that I'm typing this on, so since I can't run bgb, I have to go with mobile emulators), so I can't figure out things like specific effect pointers on glitch items. I've mostly done the GlitchDexES because I've been learning Spanish and like to play video games in Spanish over the summer so I don't forget everything I learned the previous year. (Obviously I don't end up using most of what I learned in class in the game, but just more exposure to the language helps, especially compared to the nothing I'd otherwise be doing) I've cleaned up and filled out some of the DecDex just because there's nothing else to do. --Bwill11 06:43, 27 August 2019 (-06)
| |||