A Guide to Creating Rock Band 3 Custom Songs

Discussion in 'Wii - Tutorials' started by HarvHouHacker, Mar 31, 2019.

?
  1. Yes, it works perfectly!

    0 vote(s)
    0.0%
  2. Yes, but my songs are buggy.

    100.0%
  3. Well, yes and no. They show up, but I can't play them.

    0 vote(s)
    0.0%
  4. No, it didn't work! :-(

    0 vote(s)
    0.0%
  1. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    This is a repost of my wiki page for the GitLab repository "Rock Band 3 for Wii - Custom Songs". There may be more recent changes since this tutorial. Please visit the wiki page for the latest version.

    Some markdown characters may be left in this tutorial (`code` *italics* **bold**), as this is a direct cut-and-paste of the GitLab wiki page. Most have been edited out and replaced with BB coding ([COLOR=#15C600]code[/COLOR] [I]italics[/I] [B]bold[/B]), but if some markdown characters are still left, you may safely ignore them.

    Modified from the ScoreHero forum post, with a little help from Custom Creators. For that post, go to ScoreHero. For the Custom Creators thread, click here. This combines the two in an effort to be as concise as possible.

    This guide should help you be able to build your own customs, and import songs from other titles. Although this guide is mainly for the Wii, this should work on the Wii U as well.


    • Terms You Need to Know
      • NAND: The Wii's internal storage. Normally it is about 200MB (larger for the Wii U). It is not advisable to use this for DLC unless you are on an emulated NAND, however for those daredevils, there are some instructions here on how to do just that.
      • DLC: Download content. The Wii needs to see 2 files per song; one with metadata info, and the other with song data. There are also upgrade files, which add harmony to songs that don't support it, or support for Pro instruments.
      • .APP: A container for DLC loaded directly from the NAND. It is possible to inject this into real NAND, but it's safer if you're using an emulated NAND.
      • .BIN: A container for DLC, only for the SD card. Real NAND users may prefer these files over APP files.
      • Ticket: A file stored on the Wii which allows you to purchase and repurchase songs. You need this to pack your own DLC if you're using an SD card.
      • Content Generation: Folders on the SD card such as sZAE, sZBE, sZCE, etc. that hold about 500 files each. Each generation needs different files, but this guide will focus only on sZAE. On the NAND, DLC folders appear in hexadecimal, such as 735A4145 (which is hex for sZAE).
      • .DTA: A file that contains meta information on songs. They are not entirely cross-console compatible.

    • What You Need

      • A Wii or Wii U. D'uh! See the next section on modding it.
      • A computer with Windows XP or higher on it (Windows 7 recommended). You can try to use WINE on Linux or something similar on Mac, but the results may vary. Make sure to configure WINE to have access to your SD card and project folders before starting!
      • An SD card compatible with your Wii. If your Wii is SDHC compatible (Wii version 4.3 or Wii U any version), 4 GB minimum is recommended. You'll also need an SD card reader for your PC, if it doesn't already have one.

      Modding Your Wii

      To begin, you must find out what the state of your Wii console is. It could be:
      • Unmodded ("virgin" Wii). If you never hacked it and don't have the Homebrew Browser installed as one of the channels, you more than likely have an unmodded Wii. This is especially true if you've factory reset it, or got it unused and in the original packaging.
      • Softmodded on real NAND, using SD Card. You have hacked it, or a previous owner (if you got it from Craigslist or eBay) hacked it. You are still using the internal storage, however.
      • Softmodded on emulated NAND. You have hacked it, or a previous owner hacked it. You are emulating the Wii interface with something like USB Loader GX, which means modifications are stored on the SD card or an USB drive.
      If you've never softmodded your Wii before, WiiBrew.org has a variety of exploits you can use . The Wii and Wii U are super-easy to mod, but keep in mind that some exploits don't work for Wii Mode on the Wii U. The most important part of that site is to get The Homebrew Channel installed, make a NAND backup of your console, and get WADs installed.

    • Preparing the Custom Song Building Environment

      Get the tools

      Download the master branch of this repo (https://gitlab.com/HarvHouHacker/rock-band-3-wii-custom-songs). I recommend either a ZIP or using git clone.

      There are several packers included in this repo. RBWii-DLC-Packer-SZAE is the most complete, and should contain all the files you'll need to pack custom songs and upgrades, including a few samples from the Rock Band Harmonies Project.

      • You'll need the Wii common key, in binary format. One is included in the repo, but if you want a more unique key, ShowMiiWads can create one for you. For the latest version of ShowMiiWads, go to Sourceforge. It should have no file extension and be called "common-key". If it adds an extension, rename it without one.
      • FS Toolbox is included in the repo. While most of the instructions are written for FS Toolbox, you may find it easier to use WiiXplorer. Again, download from Sourceforge for the latest version.
      • If you've never had any DLC for Rock Band 3, you'll want to start by installing sZAE.wad from the RockBand-WADs folder using a WAD installer, like Some YAWMM Mod. Look for and download the latest release.

      Installing Homebrew Channel Programs

      The programs FS Toolbox, xyzzy, WiiXplorer, ans Some YAWMM Mod are for the Homebrew Channel. To install and use them:

      1. On your computer: Insert your Wii (or Wii U) SD card. If there isn't a folder named apps, make one. Move the entire folders of the programs you want to use in the apps folder. For instance, the FS Toolbox program will be in SDCARD/apps/fs-toolbox. If you don't know which ones are for Windows or Homebrew Channel, check for a boot.dol file. If it's there, it's for the channel; if there are .exe files, it's for Windows. If there's both, the folder may need to be sorted. To test them, unmount and eject the card.
      2. On your Wii: Put the card in your Wii and launch the Homebrew Channel (on the Wii U, launch Wii Mode first if you're not in it already). The apps should appear as a list. If they don't, check to make sure they are in the right folders and that each one at least has a boot.dol file. Keep in mind that some apps don't have descriptions or icons to identify themselves.

      Get the songs you want

      You can either repack official DLC, or pack a custom-made song.

      Get official DLC songs

      Please note: To prevent piracy, the files from official Rock Band DLC (especially .mogg files) are intentionally left out of this repo. In order to add the songs for official DLC, you must have the files from Rock Band discs or official Rock Band DLC, if you have them. To get the song data you need from Wii discs, you'll need to learn how to extract .ark files and use ArkTool (my wiki page on GitLab covers this).

      The files on here are an older version of the Rock Band Harmonies Project, and are partly needed for database files (.dta), especially when extracting from disc. The remaining files can be used to upgrade existing songs in your Rock Band 3 library. You can either download one of the song branches in this repository, or download from the Rock Band Harmonies Project on GitHub. They should be able to be used as DLC for the Wii version of Rock Band 3.

      Get custom songs

      It is very easy to find custom songs for Rock Band 3 version. There's an extensive list on Customs Creators, available in various formats. Note that there may be some with dead links, so do some web searches if a song you want isn't available. Find and download one you like.

      Xbox 360 customs are usually in CON format. You can use the C3 Con Tools to extract or simply convert the package. If you converted the package, you don't have to sort the files, as they should already be structured properly. Simply move to the packer folder, rename the folders , and skip to "Execute the Packer".

      Get your Wii Rock Band 3 ticket and keys

      You'll need the ticket from the sZAE category. This requires that you've played Rock Band 2 (two, not three) at least once on the target Wii, and that you have DLC from it (every other category, from sZBE onwards, is specifically for Rock Band 3 DLC, while both 2 and 3 share sZAE). If you never got DLC, or don't know if you have DLC for sZAE, follow these steps:

      1. On your computer: Put sZAE.wad on the SD card. You can make a wads folder to put it in, if you like.
      2. On the Wii: In the Homebrew Channel, load Some YAWMM Mod. Select Wii SD Card Slot, then navigate to the WAD you added. Select it, then select Install WAD. You'll get a -1022 error. Select it again, and choose Uninstall WAD. Then, install it again. You'll get the same error. Believe it or not, it actually succeeded!

      Once you have done that, you should now be able to get a ticket.

      1. On the Wii: Put the SD card in. Launch the Homebrew Browser Channel.
        - Using FS Toolbox: Navigate to /ticket/00010005. Highlight 735a4145.tik and press - on your Wii remote to copy the file to your SD card.
        - Using WiiXplorer: Navigate to NAND:/ticket/00010005. Highlight 735a4145.tik and press +. Select copy, then navigate to your SD and paste it there. If you like, you can create a folder called "RB3_Stuff" or similar and paste it in there.
        - After doing either option, take out the SD card.
      2. On your computer: Plug in the SD. Navigate to FS-TOOLBOX/ticket/00010005 if using FS Toolbox, or wherever you put it if using WiiXplorer. Rename 735a4145.tik to title.tik and put it in the root of the RBWii-DLC-Packer folder.

      If you're doing real NAND, you'll need an unique console ID key. This is an 8-digit hexadecimal number.
      • The easiest way is to use xyzzy, included in this repo. Launch it from the Homebrew Browser. It will not only show you your console ID, but dump it to a file as well.
      • If you've recently backed up your NAND, you should have keys unique to your console. I may explain in a later update to the wiki how to access them.
      • You can also find your console ID by using a hexadecimal editor to open any DLC you may already have and write down (without spaces) the part highlighted in the following image. It must be 8 characters long.

      [​IMG]

      Get your console ID and paste it in ng_id.txt.

      A title.tmd file is included, as well as the DLC save file 000001D2.app. However, if you'd rather use your own, navigate to title/00010005/735a4145/content in either FS Toolbox or WiiXplorer and grab both files. You may need these for packing DLC.

    • Learn The Packing Structure

      Here is how your folder should look like with everything in it.

      [​IMG]

      Observe the naming convention examples used to help you see important values directly from the file name. For instance, let's take a look at how 061_0000003d_upgrades is titled. The first digits (061) of the folder name are in "normal" base ten, the actual number of the song. The next eight digits separated by the underscore (0000003d) is the hexadecimal number of 61. The last part is the type of DLC that it will make (upgrades). That part can be preceded by another name separated by an underscore, like "mysong", so it reads 061_0000003d_mysong_upgrades. This folder will pack to 0000003d.app for adding directly to the NAND, which will then be used for creating 061.bin for the SD card. Even if you're on emulated NAND, you still need to keep track of the .bin file name.

      The first folder in the sample (001_00000001_spoof) has a spoof file required by RBHP. It is simply a songs.dta file which can contain updated DTAs to force harmonies to load on upgraded songs. You need the Wii version of the DTA to upgrade songs, though. This spoofing file is set to overwrite song 001, "The Kill". You can find out which songs will be overwritten by seeing the archived RawkSD Master DLC list. If you do have that song, you'll have to overwrite it and add it back some other way. If you don't, you can force an overwrite on another DLC. If you have no DLC yet, don't worry! There's about to be a remedy...

      Folder 002_00000002_upgrades contains, naturally, more upgrades. You can add in your own Pro Guitar and Harmony upgrades here, as long as you update the upgrades.dta correctly. Wii requires the file path to contain dlc/sZAE/002/content/songs_upgrades/. For content to be found, you need to include the content generation title and the number of the folder it's in, which in this case is 002. After that path, you then add the upgrade midi's name, such as song_plus.mid.

      There's a limit of about 13 song upgrades per pack, so make another folder when needed.

      Packing Your Own Songs

      In the RBWii-DLC-Packer-sZAE folder, we'll make this song 063/064. Make 2 folders and call them:

      Code:
      063_0000003f_songname_meta
      064_00000040_songname_song
      ...Where songname is the condensed title of the song, i.e. detroitrockcity. Remember, the name order is song number, then hexadecimal equivalent, then an optional title, then the type of folder, which in this case are "meta" and "song". Your song doesn't have to be in the list to be added; just assign it any number you wish. It can even be an official DLC out of order, with this method!

      Note: If you downloaded a custom from Customs Creators, the folders should already be structured. Just rename the folders, move them to the packer directory, and skip ahead to section "Execute the Packer".

      Open the meta folder and make the folders to match the structure below. Copy the files for the song you chose into the folders as shown.

      Code:
      >content
       >songs
        *songs.dta
        >songname
         *songname_prev.mogg
         >gen
          *songname_keep.png_wii
      An `*` indicates a file, while a `>` indicates a folder. The following files and folders indented after a folder indicate what's supposed to be in it.

      • If you don't have a .png_wii file, you can make one using Album Make (see section "Make Album Covers").
      • If you don't have a songname_prev.mogg, you can make one with an audio editor. Because the Wii can't play the preview from the full song file, the preview mogg gets priority. It can be a mono ~10 second clip of the song in mogg format. You may have issues if you had to create the preview .mogg file. If, once installed on the Wii, the song doesn't appear, it doesn't play right, or the whole Wii freezes when the song is selected, delete the preview, repack, and re-add to the Wii.

      Now open the song folder you made for 064 and create the following structure. Drop the files where they are necessary.

      Code:
      >content
       >songs
        >songname
         *songname.midi
         *songname.mogg
         >gen
          *songname.milo_wii
      In some Rock Band discs, i.e. Rock Band 2, you'll see a songname.bik in place of the .mogg file. This can be used, as well.

      Normally, custom songs from places like Customs Creators come with .milo_xbox files, and renaming them to .milo_wii seems to work just fine. Now you should have all the song files moved in the appropriate DLC folders.

      Go back to the songs.dta file that was placed in the meta folder and open it in a text editor. In the name path, just like what had to be done with the upgrades.dta path, you have to add the Wii-specific path so it reads as dlc/sZAE/063/content/songs/songname/songname. The file has to point to the meta folder we created.

      You can pack multiple songs into this file structure, though there is a limit of about 400MB for .APP files and 40MB for .BIN files.

    • Execute The Packer

      Use either the batch script file Packer_Script.bat or the packdlc.bat generated by Packer_Script_Creator.exe to start the packing process. Both use u8it.exe to make .app files and wadpacker.exe to turn them into .bin files.

      Using the Packer Script Creator

      If you'd rather do it the easy way, simply click on Packer_Script_Creator.exe to generate a packdlc.bat file, then click on the batch file it created to create your .app and .bin files. The benefit of this is that it automatically adds extra lines of code for you, to remove unneeded files automatically created by the packers.

      Editing and Running the Packer Script

      If you want to better control what gets packed, you may prefer modifying Packer_Script.bat, as running the automatically generated packdlc.bat script will pack every DLC, every time. Open Packer_Script.bat with your text editor. Notice that there already are some lines of code:

      Code:
      @echo off
      
      REM This packs files for emulated NAND.
      u8it 001_00000001_spoof 00000001.app -pack
      u8it 002_00000002_upgrades 00000002.app -pack
      u8it 061_0000003d_upgrades 0000003d.app -pack
      
      REM This packs files for real NAND.
      wadpacker 1, 2
      wadpacker 61, 1
      
      REM If you want a more verbose output, delete the "@echo off" line.
      Erase the line to pack 061 and add the folders we created under the emulated NAND part to read like so:

      Code:
      u8it 063_0000003f_meta 0000003f.app -pack
      u8it 064_00000040_song 00000040.app -pack
      This part is needed even if we don't want to use the .app files, because they'll be used for making .bin files.

      The last part of the batch command is split up in 2 commands because the tool stops when more DLC can't be found. Retype the last part at the bottom to pack 063 and 064.

      Code:
      wadpacker 63 2
      Now, if you ever have to add more songs, in 065/066 and on, you increment the second number for every file you make. Thus, changing it to wadpacker 63 4 would pack 4 files starting with 63, and so on.

      Save that and run pack-dlc.bat. If it was done correctly, you should now have .app files and .bin files.
      • Real NAND SD users will take the .bin files and place them in the sZAE folder of their SD card (private/wii/data/sZAE).
      • Emulated NAND users should take the .app files and put them in title/00010005/735a4145/content using FS Toolbox or WiiXplorer. This can be done on real NAND too, but be sure to put only the .app files there and not other files, or you may corrupt your game!

    • Reset the Cache

      Finally, every time you add new songs or change the contents of a DLC slot, you must reset the song cache.

      • With FS Toolbox, navigate to title/00010000/535a4245/data. Let it create those folders on your SD, then put the clean MSTORE.vff file from this repo in the data folder and repeat. Press + to replace the file.
      • With WiiXplorer, go to Settings > Boot Settings > NAND Write access. Select "Yes" and "Accept". Then, navigate to title/00010000/535a4245/data and delete MSTORE.vff. This will force the software to recreate it.

      Running the Game

      Depending on your configurations will depend on how you run the game. In most cases, a USB loader may be needed. Download USB Loader GX from SourceForge or Configurable USB Loader Mod from WiiDatabase (German site).

      Your DLC:

      • If you put the DLC on your SD card expecting it to automatically work with Rock Band 3 when loading it from the Disc Channel, you will receive the "Add-on Content cannot be restored to the Wii System Memory" message when it tries to load it after selecting your profile. This may be due to Rock Band 3 detecting mismatched song IDs (since this guide allows you to assign a number set to any song). Use a homebrew USB loader instead.
      • If you injected the .app files into your NAND, the songs will appear and be playable. This will work for real NAND users.

      Your NAND:

      • If real, using .app files will work, even when loading the game from the Disc Channel, however not very many songs will be able to be played all at once using this method. Using .bin files are better, since you can load more songs that way.
      • You can run games from an emulated NAND, however this definitely requires a USB loader of some kind. Some loaders will dump the real NAND for you so that you can use the dump as an emulated NAND. Make sure the SD card or USB storage device that you will dump the NAND to has room for at least 4 GB or more!

      Your Game:

      • If using a physical disc, any of the above configurations will work, however you will not be able to modify anything that is on the disc directly.
      • Some loaders can rip game discs in the Wii U to an ISO, WBFS, or other disc-type file, but in order to use them, a USB loader is necessary. Also, you need room on an SD card or USB storage for as much as one DVD (approx. 4.7 GB). Burning the file to a DVD and trying to run it that way will not work, as the disc will not be able to be read.

      Upon launching the game, if you followed all the instructions carefully, your songs will appear and be playable. Any known issues (with workarounds) are at the bottom of this tutorial. If anything goes wrong, leave me a comment or check out my GitLab issues.

    • Videos

      Cache resetting:

      Video proof of an imported song working, with RBHP upgrades included:

      This shows a RB1 song playing flawlessly in RB3 Wii:

    • Make Album Covers

      The Wii can't use Xbox album art files, so you have to make your own. Album Make, included in this repo, is very easy to use. Find the album art you'd like to use and resize it to 128x128 and save it as a PNG. Drop this file in the input folder. Now, run AlbumMake to batch convert everything. You can pick up your usable .png_wii file in the png_wii folder.

    • Known issues

      Please see my GitLab Snippet or GitLab Issues page.

    If you have any problems, discuss it here, mention me in a new thread forum (with @HarvHouHacker), or post an issue on my GitLab repo.
     
    Last edited by HarvHouHacker, Apr 15, 2019
  2. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    You may suggest edits, if you see something wrong. I'm still testing to see what works and what doesn't, so this tutorial may not be 100% accurate.

    Also, the linked repo does not include PAL Wii specific DLC packers, although the guide should work if you find some. Just remember that content generation ends in P, not E. Thus, sZAE for PAL would be sZAP.
     
    Last edited by HarvHouHacker, Mar 31, 2019
  3. FancyNintendoGamer567

    FancyNintendoGamer567 GBAtemp Advanced Fan

    Member
    4
    Feb 13, 2017
    United States
    Interesting, if Rock Band works w/o a guitar I might try this.
    Also I know what most of these are, just saying.
     
  4. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Last edited by HarvHouHacker, Mar 31, 2019
  5. FancyNintendoGamer567

    FancyNintendoGamer567 GBAtemp Advanced Fan

    Member
    4
    Feb 13, 2017
    United States
    But I mean like, with a WiiMote but ok.
     
  6. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    What, you mean just the Wii remote? I think you need to have a Rock Band instrument, although a Guitar Hero instrument might work (I don't have one, so I've never tried it).
     
  7. Atomzk

    Atomzk Newbie

    Newcomer
    1
    Mar 31, 2019
    Mexico
    Its so interesting how rockband 3 get this kind of replay value... I love the game, and since last months my friends come to my home to play it because ive all the instruments and some DLC.
    I will try to follow this tutorial and add more songs to my playlist.
     
    HarvHouHacker likes this.
  8. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    You do that! If something goes wonky, let me know please. I can adjust the tutorial as needed (if you need more help, please visit my wiki).
     
  9. Atomzk

    Atomzk Newbie

    Newcomer
    1
    Mar 31, 2019
    Mexico
    There is some form of copy my DLC songs to another Wii SD??
    Maybe to share all my content (around 100songs) to the community?
    I read something about the usage of YABDM, but there´s no tutorial to follow.
    I have a backup of my SD "private" folder in PC.
     
  10. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    First, are you asking if the DLC you got from one Wii console will work in another? I don't know how to answer, as I haven't tried.
    Read my piracy warning, in regards to sharing songs.
    I have never used Yet Another BlueDump Mod, however it is not necessary for this tutorial. If you're using it to try to convert DLC to WADs, I'd have to do more research in order to help you.
    Keep your backup, in case something goes wonky.

    EDIT: What's with me and "wonky" lately? I've used that twice already...
     
    Last edited by HarvHouHacker, Apr 1, 2019
    Atomzk likes this.
  11. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Repo Update
    • I added a new executable to the sZAE packer! It's the "RB3WiiPackTool.exe" from the other packers in the beta_software branch, but renamed to "Packer_Script_Creator.exe".
    • I renamed "pack-dlc.bat" to "Packer_Script.bat", in an attempt to avoid confusion with the "packdlc.bat" generated by the Packer Script Creator.
    • The wiki guide was updated to reflect changes in the repo.
    If you are using git pull to get the software, I suggest you run it again to get the new changes. Else, download a new ZIP, extract it to your project directory, and let it overwrite your existing files.
     
    Last edited by HarvHouHacker, Apr 7, 2019
  12. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    If anyone knows how to fix the SD card problem, I'd love to know how!

    EDIT: Fixed, but now the instruments won't play! I'm gonna create a new issue based on this.
     
    Last edited by HarvHouHacker, Apr 7, 2019
  13. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Wiki and Tutorial Updates
    I added a new section in the tutorial about how to run the game. You can run the game using any USB loader (USB Loader GX and CFG USB Loader are two I've tried). If you have instrument problems, I can not help you. I posted a GitLab Snippet warning those about inferior powered USB hubs.

    EDIT: The section in the wiki is now more descriptive. This may or may not be reflected in the tutorial.
    RE-EDIT: Reflected.
     
    Last edited by HarvHouHacker, Apr 7, 2019
  14. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Repo Update
    • Some READMEs have been added throughout the repo for your convenience.
    • I modified some files in the beta_software branch; I'm thinking of moving the DLC Packers there to the master branch eventually.
    If you are using git pull to get the software, I suggest you run it again to get the new changes. Else, download a new ZIP, extract it to your project directory, and let it overwrite your existing files.
     
    Last edited by HarvHouHacker, Apr 7, 2019
  15. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Some minor fixes in the tutorial were made recently. I tried to remove the markdown characters. Also, I added a splash of color. :-)
     
    Atomzk likes this.
  16. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Tutorial Update
    Now with tabs! You can navigate the tutorial better (I hope)!

    I've been doing a lot of work on the tutorial lately, mainly because I want to be able to leave it in a state where it can still be used weeks, months, years from now, despite not being as up-to-date as the GitLab Wiki which I'd rather maintain. Hopefully, the tabs will help those who need just certain sections of the tutorial. If it doesn't look right, I can adjust it a bit more. Just let me know!
     
    Last edited by HarvHouHacker, Apr 8, 2019
    Atomzk likes this.
  17. Atomzk

    Atomzk Newbie

    Newcomer
    1
    Mar 31, 2019
    Mexico
    i will follow the entire tutorial hopelly this weekend!!
    Then of course make the respective sightings
     
    HarvHouHacker likes this.
  18. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    You can follow either the tutorial or the wiki. The wiki is updated more frequently, but the tutorial is cooler because it's tabbed and colorful. :D
     
    Atomzk likes this.
  19. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    How's it workin' for ya?
     
  20. HarvHouHacker
    OP

    HarvHouHacker Advanced Member

    Newcomer
    1
    Mar 24, 2019
    United States
    In broken computer chip land.
    Tutorial Update
    Issues have been removed from here; follow the links to see the current issues.
     
Loading...