by sairugoth at 12-22-2017, 02:30 AM
I'm really in to "Hunter x Hunter" right now but, currently I'd have to say its "My Hero Academia".
[Image: 27441?size=1600x600&region=US]
This anime is just bursting with emotion and energy and I freaking love it. One of the best I've seen in years. If you haven't seen it, go watch it; its good.

Whats your favorite anime?
by /Zel/ at 12-15-2017, 03:25 AM
Since this new forum was released I figured I might as well contribute something. Lately I have been making Sketchup Renders of some of my models, so I figured I might as well share them here. Tell me what you think!

3D Tower of Hera:
[Image: Render_2.png]
[Image: Render.png]

Light Shrine (Name not final)
[Image: Render_3.png]
[Image: Render_4.png]
by GodsTurf at 12-13-2017, 12:08 AM
[Image: 3sDOrNs.jpg]
[Image: 4CQXDA3.png]
The ring around your profile icon is mishapen when the aspect ratio is abnormal.

KEYWORDS: Bug, Profile, Icon, Chrome, Silk, Mobile, Window, Windows

PLATFORM: Chrome on Windows, Silk on Mobile


URL: All



It appears to occur when the window width is a certain degree thin. The bug appears to be unrelated to the window height. This bug does not occur in any form when the window is wider than normal.

Results appear to be purely aesthetic, no functional bug appears to be present.
by Spire at 12-11-2017, 11:00 AM
KEYWORDS: UI , Text , Attachments , Attached , Files , Overlap , Thumbnail , Post , File

MODE: Thread
URL: Any

When viewing a post that contains an attachment(s), the text 'Attached Files' overlaps 'Thumbnails', but is otherwise functional.

1. Open Chrome
2. Navigate to thread with Attachments at Hylian Modding
3. Observe issue within post(s) of interest

Overlapping text exists in Posts with Attachments.

No text overlaps unless intended.

  • Screenshots attached.
by Spire at 12-11-2017, 09:35 AM
Hello, and welcome to Bug Reporting. If ever you encounter a glitch/error on the site, that is a Bug - and if you feel inclined, if any-where or by any-way, please document it here. Below is an ever-growing outline of how to properly document and report a bug. There is no guarantee we can fix anything or everything, but I'm sure we can fix some things along the way. This is a learning process in growing a new community from the persistent and mutual passions presented in our parallel projects.

THREAD SUBJECT: The Summary of the Bug, separated in parts is composed of "Issue Category - Cause/Effect or Effect/Cause", i.e. "Member List / UI - Page 4 does not show Avatars".

KEYWORDS: Characteristics or elements of the Bug, useful when searching for bugs if and when we find numerous, and there most likely will in the instance of us releasing new themes and such without deep testing, i.e. "Member , List , UI , Avatar , Display , Load , Missing. Be efficient in your use of words by selecting those that best describe the issue and thus, require the least amount thereof -- however, unless you are being intentionally disruptive by adding an incredible amount of keywords that makes this one bug surface in most searches, then adding more than a few keywords is o-kay.

PLATFORM: Your browser and optionally your OS and device.

MODE: The type of page you are on

URL: The URL(s) of the problematic page(s). If it is a universal issue, 'Any' or 'All'.

M: M is for MegaBug. A MegaBug is one of two things: a problem so massive with site operation, you probably won't even be able to report it, but even more importantly: Legal — This is of utmost importance. We are treading a fine line by modding existing Zelda games as-is, so, if you see something on the site that even seems illegal, bug it. We'll look into it and if we decide that it is, shall remove it.
A: Crash/Freeze/Loss of Total Control/Inoperability/Oblivion
B: Functional Errors: Accessibility, Unresponsive Options/Controls, Attachment/File/Download Errors, etc.
C: Graphical/Audio Errors & Errors in Official Announcements/Posts (if you see one we didn't catch, please report it!—and by official, that doesn't mean everything Staff Members write)
D: The tiniest things. Like, if a pixel in a graphic is off.

Always | Often | Sometimes | Rarely | Can't Reproduce; use your discretion for the values thereof.

Describe what the bug is. Save the method. Use this field to list attributes however you feel are needed.

List the steps in a columned numerical list, detailing exactly how to reproduce the bug beginning with the URL.

Describe the results of the bug, including the effect(s) it has on the site.

Describe what you expect to happen when you perform the action that triggers the bug.

Any additional information may be input here, typically bulleted, but add it as you please. Attachments appear as small thumbnails so it's easy to overlook them, as such, if you have attached something to the bug, please write something to the effect of 'Screenshot attached'. And keep the files as small as possible without diminishing the evidence. Feel free to draw on the images in order to highlight errors; bright, neon colors work well when boxing fields, pointing arrows, and writing notes.

Here is a template for the Bug Format. The more you write, the more you'll remember:








And that's it! If you have any questions, please ask. Happy hunting,

[Image: latest?cb=20100328014204]
by Spire at 12-11-2017, 08:08 AM
KEYWORDS: UI , Quick , Edit , Post , Highlight , Scroll , Refresh , Page
MODE: Thread
URL: Any

When Quick-Editing a post, the UI can totally lock up, requiring you to wait for one of three things to happen:
  • It remains locked, requires refresh.
  • It opens the Quick Edit window and displays 'Loading...'
  • It resolves itself.
1. Open Chrome
2. Navigate to
3. Open a thread
4. Post a comment in said thread
5. Select the Edit Button in bottom-right corner of post estate
6. Select Quick Edit
7. Observe the bar highlights, the cursor sticks and/or that scrolling or any interaction with page is inoperable
8. Refresh page/close tab

While browsing Hylian Modding in Chrome, clicking 'Quick Edit' on a post can lock up the UI, requiring a refresh of the page.

Selecting Quick Edit does not lock up the UI.

  • Screenshot attached.
by Psi-Hate at 12-11-2017, 04:17 AM
This mini mod is simply something I've had untouched for about half a year. Essentially it's a proof of concept dungeon using the birds-eye-view camera. It's short, but it's a decently put together concept demo made within a few days. 

Setting it up

Go to CloudMax' Rom Patcher and drag your clean OoT Debug ROM and the supplied .txt patch. The website will patch the ROM and will have you automatically download the updated ROM. Simply run the ROM in an emulator of your choice (make sure you set RAM to 8mb!). 

Playing it

Select File 1 and go to Spot 117. Enjoy!


by Psi-Hate at 12-11-2017, 02:31 AM
This mod allows up to 4 Links to solve a series of dungeons. The dungeons are themed like the original 3 dungeons of OoT. First is the Deku Tree, then Dodongo's Cavern, then the Ice Cavern. 
You start out in a hub area. The 2nd and 3rd dungeons are blocked off, requiring items that you get in the previous dungeon to obtain access to them. 

This mod is not hardware compatible, but for wiiu/emulators, it is compatible. (Emulator MUST be NEMU or PJ64 1.7!!)
The download for the full package lies in the description of the trailer (includes Rom and Emulator).




Psi-Hate - Maps, planning, editing, etc
MelonSpeedruns - Maps, Camera, importing, etc
z64offline - Hub concept
TyroneAnderson - Ideas and Help
ThreePendants: Exits and stuff
Spinout182: Four Swords Mod
JMan: GS codes
by Psi-Hate at 12-11-2017, 02:14 AM
Modifying the entrance table is a must when connecting your new (or even just modified) world together. Without editing the entrance table to abide by your changes, you won't be able to connect your maps and spawns the way you want. 


The entrance table can be thought of as a big list of all possible locations that Link can spawn at; it also controls certain aspects of map transitioning.

Every scene has at least four entrances per spawn: young!day, young!night, adult!day, adult!night
This is because every single scene has at least four states, corresponding individually to the time and age of Link. Some scenes have more entrances because of cutscenes.

Below is an example of an entrance:

"01 00 41 02"

Every entrance is formatted like so:

Where XX = Scene || YY = Spawn/Entrance ||  ZZZZ = Variable

So for example...

[Image: B0xEwPr.png]

"3B" being the scene number in hexadecimal, "01" being the spawn, "4102" being a bitpacked variable.

Bitpacking means that a variable is made up of smaller variables that are only a few bits long. These are packed into one variable which is represented in hex.

Each entrance can be represented by an index. Think of an index as the position of an entry in the entrance list. All indices are in hexadecimal, meaning the first entry would be "0000", and the tenth entry, for example, would be "000A". 


The Entrance Table starts at 0x00B9F360 within the ROM.

1. Take the scene you want to create a entrance for, and convert it's scene number from decimal to hexadecimal (for example: scene 108 would translate to 6C in hex)

2. Write "XX YY ZZZZ" (inserting your own values into the placeholders), making sure to write it 4 times total for each spawn.
(for example: lets say we are exiting from fishing pond and are entering the first spawn of our custom map injected to scene 108, we'll write "6C 00 41 02" and write it a total of 4 times down the line).

3. Since you now have edited your entrance table to whatever extent, you'll need to edit your scene to accommodate these changes. Edit the scene's exit list and write the index of your entrance, making sure the order of exits in polygon types correspond to the order of indices in the exit list. For example, a polygon type with exit 04 would correspond to the fourth index in the exit list. 


4. Review and think through your work. You should be able to look at the entrance table you made and figure out what the destination is and where specifically it'll take you within the scene. Make sure you don't get anything mixed up as it's a hassle to debug, so keep track of every edit you do.

That's about it!
by Psi-Hate at 12-10-2017, 11:38 PM
The default camera angle of a scene is a third-person behind-the-shoulder view.  The current tools out there don't allow you to easily change the camera settings, so you'll need to use a hex editor. This can be a bit difficult if you're not sure what you're doing. 

Do not fear, for I am here!... to write tutorials of course!

Anyway, let's get to business.


On CloudModdingWiki, there is a page over the scene format in which there's a camera function that you'll be able to manipulate using the criteria and documentation listed there. For those who aren't familiar, I'll be showing the process and explaining what each important detail is.

1. Find the 0x03 scene header command in your scene file (Search "03000000"). This points collision header. 

2. The 0x03 command begins with  0x03 (sets up the command and tells the game this will point to the collision header), followed by three bytes of padding (useless 0s), and ends with a four byte segment address. The segment address is what the game will be reading to find where the collision header is located.

Segment addresses have two parts: a segment ID and an offset. The segment ID references a table of start addresses kept track of by the CPU, usually corresponding to important files in memory. The offset is then relative to these start addresses. There are 16 segment IDs in total. 

Segment Address Table

For example: "0x02000069" has a segment ID of 0x02 and an offset of 0x69. This means that the game will jump to the start of the current scene (Segment ID 0x02 = Current Scene) and move 0x69 bytes forward. It will then read data from there on. 

Knowing this, go to the segment address defined in the 0x03 command.

3. After you go to the specified offset, you'll find the collision header. It is formatted like so:
bbbbcccc ddddeeee ffffgggg vvvv0000
aaaaaaaa pppp0000 llllllll tttttttt
xxxxxxxx wwww0000 mmmmmmmm

This is what it may look like in the file:

[Image: ViRvjRJ.png]

"xxxxxxxx" is the segment address for where the camera variable is set. 

4. The segment ID in the picture above would be 0x02, and the offset would be 0xC770. This means that we must go to that offset and write the camera option that we want. There are many undocumented camera options, so in the future this tutorial will be updated with a more comprehensive list. However, here are some currently discovered options: 

Camera Options
That's about it! Here's a basic rundown: 

1. Open the scenefile in [Preferred Hex Editor]
2. Search for "03000000"
3. Find "0200xxxx"
4. Copy xxxx and go to that offset
5. Find "0200yyyy"
6. Copy yyyy and go to that offset
7. Write the camera variable you want set
8. ???
9. Profit!
Welcome, Guest
You have to register before you can post on our site.


Search Forums

Forum Statistics
Members: 331
Latest member: hyruletom64
Forum threads: 60
Forum posts: 161
Online Users
There are currently 8 online users.
0 Member(s) | 8 Guest(s)