Code Crediting Rules Thread
#1
Video 
Proper Credits Format (listed after/below Code):

Code created by: John Example
Code contributor(s): Josh Example, Bob Example

This format doesn't have to 100% exact. For example you can put 'Code Creator' instead of 'Code created by'. Also, you can put something such as 'Code credits' instead of 'Code contributor(s)'.

NOTE: Do not put any credits/contribution notes for Porting. Porting is nice and I love to port, but it has no business being in the credits for actually making the code(s).

What actions qualify a person as a Code Contributor aka be listed in the Code Credits?
Any person who has done at least one of the following....
- Helped made the code
- Helped find the RAM Address
- Helped fixed a non-working/partially working code
- Shortened/Optimized the source of an ASM (C2/C0) code (read BLUE note below for more info!)

---

This does NOT include somebody modifying a floating value of a code.

If you make a totally new code that uses an already found address, the original address founder must be listed as the code contributor.



NOTE About Those Who Nop Address's Already Found By Someone Else, or Modify a Floating Point Value on an already discovered Address!!:
If you nop an already discovered code address to 'make' a new code, you DO NOT get credits as the creator of the code, and you DO NOT get credits as code contributor. Period. Noping an address takes no skill. You can still post the thread of that code with a nop if it doesn't exist, but the original address founder must obviously be listed as the code creator!

Same rules apply if you make a code have a 'new effect' by finding an unused floating point value to an already discovered code address. Once again, you DO NOT get credits as the creator of the code and you DO NOT get credits as a code contributor.

About 'trying/plugging-in' other values/instructions on an already found code address/single-liner code:
Any other values you use on an already found address (such as 38000000 or 2C000000, etc etc) is OK for you to put yourself as the Code Creator. HOWEVER, you must remember to add the address founder as the Code Contributor.



Important Info Regarding ASM (C2/C0 Assembly Codes) Codes; NOTE: you may not understand some of this if you are not familiar with ASM! These notes are for real Code Creators!!

If new instructions are added/removed from an assembly code but the code functions the same, you are NOT qualified to list yourself as the Code Creator. Only as a Code Contributor!

If new instructions are added/removed from an assembly code and a new function/feature is added as a result to that existing ASM Code... You are qualified as the Code Creator since it is objectively a new/different code. However you MUST add the original Code Creator as the Code Contributor/Code Credits! Feel free to post a thread of the new code if one doesn't exist already.
Reply
#2
I personally think credits should be done as they are on geckocodes.

Example:

Code Name [Code Author]

(NTSC-U)

etc...

Glad you came around to adding credits though. However, as you said before, it will be hard to track down the original creator at times.
[Image: M8Vn0Cu.png]
Reply
#3
In my opinion, credits should remain at the bottom. This is comparing apples to oranges but in Movies, the credits are usually after the ending. So to me, it would make more sense for them to be at the bottom. Plus, trying to add Code Contributors with the geckocodes format would be a mess. Code contributors need their cred too.
Reply
#4
UPDATE: finished added as much code credits as possible to all the codes. there ended being just a few codes to where i coudn't figure out who made them.
Reply
#5
It appears that my (Gskartwii) Line Colour Changer (https://mkwii.org/showthread.php?tid=432) has been attributed to H3AT, while I created the original set of codes for EUR, JPN and USA.
A little bit of history regarding this:

The TRUE original source of the code: CaronHT's StaticR.rel edits: https://www.youtube.com/watch?v=Ggb1MxGjWcs (check out the comments!)
I then searched for the StaticR part that was modified in a PAL RAM dump and created the codes.
Thread where I originally posted the code, in October 2012: http://www.bullywiihacks.com/t14p120-eng...hread#4770
It was also posted on Lecce's site, correctly attributed to me: http://www.davidesante.com/t888-region-c...-gskartwii
The code was also later published on Pastebin, misattributed to somebody called "Luis35555vr" or something like that.
Then it was once again posted to Lecce's site, misattributed to H3AT: http://www.davidesante.com/t3443-color-line-all-region

In retrospect I find it interesting that the PAL code did actually work (it even says I tested it), while the offset in the code is not aligned to a 4-byte boundary. My theory is that Ocarina truncates the last 2 bits of addresses in 04 codes, but that doesn't seem very realistic. In the versions attributed to H3AT, the last 2 bits indeed are truncated. Additionally, H3AT seems to have created more codes for different regions.
Given these points, my suggestion is the following:

Code created by: Gskartwii
Code contributor: H3AT
Reply
#6
(06-17-2018, 03:27 PM)gskw Wrote: It appears that my (Gskartwii) Line Colour Changer (https://mkwii.org/showthread.php?tid=432) has been attributed to H3AT, while I created the original set of codes for EUR, JPN and USA.
A little bit of history regarding this:

The TRUE original source of the code: CaronHT's StaticR.rel edits: https://www.youtube.com/watch?v=Ggb1MxGjWcs (check out the comments!)
I then searched for the StaticR part that was modified in a PAL RAM dump and created the codes.
Thread where I originally posted the code, in October 2012: http://www.bullywiihacks.com/t14p120-eng...hread#4770
It was also posted on Lecce's site, correctly attributed to me: http://www.davidesante.com/t888-region-c...-gskartwii
The code was also later published on Pastebin, misattributed to somebody called "Luis35555vr" or something like that.
Then it was once again posted to Lecce's site, misattributed to H3AT: http://www.davidesante.com/t3443-color-line-all-region

In retrospect I find it interesting that the PAL code did actually work (it even says I tested it), while the offset in the code is not aligned to a 4-byte boundary. My theory is that Ocarina truncates the last 2 bits of addresses in 04 codes, but that doesn't seem very realistic. In the versions attributed to H3AT, the last 2 bits indeed are truncated. Additionally, H3AT seems to have created more codes for different regions.
Given these points, my suggestion is the following:

Code created by: Gskartwii
Code contributor: H3AT

You are certainly correct and I have updated the code credits, apologies for the inconvenience.

As for the memory misalignment, I double checked the PAL code in the post and it is correct. I do not think Ocarina truncates the last 2 bits of the address since I have done memory writes that are not aligned to a 4-byte boundary and they work as expected. Perhaps something changed in later versions of Ocarina or Gecko ?
Reply
#7
Updated credit guidelines about nopping address's and other little things
Reply
#8
New important notes added. Please read! Thank you
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)