Post: Destiny 1.08 RTM
Options
01-20-2015, 10:40 PM
#1
04jberry
whoo piece of candy!!!
Destiny 1.08 RTM
Description: So i used NelsonHacks Tool to get the offsets and the devcomponents dll made it look
a bit smart and idiot proof.
The CID changer has a maximum and minimum of 32 characters so you can just hold 0.
I made the 1 shot kill x10 x20 x999 so when you click either one the others disable so you may
change and they won't all be checked.
if anyone like this tool and would like me to add the visions in just send me a message and ill add em.
You must login or register to view this content.
Tool: You must login or register to view this content.
Source: You must login or register to view this content.
Description: So i used NelsonHacks Tool to get the offsets and the devcomponents dll made it look
a bit smart and idiot proof.
The CID changer has a maximum and minimum of 32 characters so you can just hold 0.
I made the 1 shot kill x10 x20 x999 so when you click either one the others disable so you may
change and they won't all be checked.
if anyone like this tool and would like me to add the visions in just send me a message and ill add em.
You must login or register to view this content.
Tool: You must login or register to view this content.
Source: You must login or register to view this content.
The following 6 users say thank you to 04jberry for this useful post:
The following 6 users groaned at 04jberry for this awful post:
01-21-2015, 07:28 AM
#11
FarSideX
I’m too L33T
Originally posted by 04jberry
That's a fair point but let me counter by saying,
in a field there is an apple tree and your quite hungry so you walk up to this apple tree and notice that there are only 2 apples on this tree, 1 of them is right at the top of the tree and will be a bit of a challenge to get but the other apple is much lower and you are able to pick it whilst standing on the ground, so which apple would you pick
and just in case you don't understand what I'm saying (the apple story is a metaphor explaining that I'm not going to start from the beginning and look for the offset myself when they are being handed to me on a platter)
in a field there is an apple tree and your quite hungry so you walk up to this apple tree and notice that there are only 2 apples on this tree, 1 of them is right at the top of the tree and will be a bit of a challenge to get but the other apple is much lower and you are able to pick it whilst standing on the ground, so which apple would you pick
and just in case you don't understand what I'm saying (the apple story is a metaphor explaining that I'm not going to start from the beginning and look for the offset myself when they are being handed to me on a platter)
But why make and release a tool that does nothing new? One that only copies 3 or 4 tools that came before it, plagiarized and nothing more. This is the primary reason I do not release most stuff and why I groaned your thread. If more people would call people on this behaviour I think many more people would release original work rather than copies of others. Why should I release anything if people such as yourself are just going to copy it to get credit for something they did not do. On the topic of credit, why not give credit where it is due rather than to those that just ripped data from other peoples work? The person that did the original work is already forgotten and credit is given to others, how fair is that?
As for the apple tree analogy, would it not be more fitting to just use a tool that already exists? Is that not on a lower branch?
I think this is the single biggest problem on NGU. I do not wish to discourage people from learning to program but you really should not publish work that contains absolutely zero new content, keep it to yourself. If you had even put a minor new hack into your tool I would give you nothing but praise, but you did not, you only copied others work.
There is a big difference in including publicly known hacks in a tool that introduces something new and making a tool that is made of ONLY publicly known hacks. The latter should NEVER be publicly released. I hope this explains why I groaned your topic.
The following 7 users say thank you to FarSideX for this useful post:
01-21-2015, 08:13 AM
#12
04jberry
whoo piece of candy!!!
Originally posted by FarSideX
But why make and release a tool that does nothing new? One that only copies 3 or 4 tools that came before it, plagiarized and nothing more. This is the primary reason I do not release most stuff and why I groaned your thread. If more people would call people on this behaviour I think many more people would release original work rather than copies of others. Why should I release anything if people such as yourself are just going to copy it to get credit for something they did not do. On the topic of credit, why not give credit where it is due rather than to those that just ripped data from other peoples work? The person that did the original work is already forgotten and credit is given to others, how fair is that?
As for the apple tree analogy, would it not be more fitting to just use a tool that already exists? Is that not on a lower branch?
I think this is the single biggest problem on NGU. I do not wish to discourage people from learning to program but you really should not publish work that contains absolutely zero new content, keep it to yourself. If you had even put a minor new hack into your tool I would give you nothing but praise, but you did not, you only copied others work.
There is a big difference in including publicly known hacks in a tool that introduces something new and making a tool that is made of ONLY publicly known hacks. The latter should NEVER be publicly released. I hope this explains why I groaned your topic.
As for the apple tree analogy, would it not be more fitting to just use a tool that already exists? Is that not on a lower branch?
I think this is the single biggest problem on NGU. I do not wish to discourage people from learning to program but you really should not publish work that contains absolutely zero new content, keep it to yourself. If you had even put a minor new hack into your tool I would give you nothing but praise, but you did not, you only copied others work.
There is a big difference in including publicly known hacks in a tool that introduces something new and making a tool that is made of ONLY publicly known hacks. The latter should NEVER be publicly released. I hope this explains why I groaned your topic.
thanks for clearing up the groan, also i must point out that i have given credit i mentioned in the thread whose tool i use and also have credited him in the tool as well.
originally i created the tool for me my friends and family to use, however thought that other may enjoy a simplified rtm tool,
also it was not my intention to plagiarize for credit, i have always tried to help people out rather than copy.
and to conclude, if you are upset because i copied someone else's work then say the words and i will take to tool off.
01-21-2015, 10:40 AM
#13
wajdi9
Space Ninja
Originally posted by FarSideX
But why make and release a tool that does nothing new? One that only copies 3 or 4 tools that came before it, plagiarized and nothing more. This is the primary reason I do not release most stuff and why I groaned your thread. If more people would call people on this behaviour I think many more people would release original work rather than copies of others. Why should I release anything if people such as yourself are just going to copy it to get credit for something they did not do. On the topic of credit, why not give credit where it is due rather than to those that just ripped data from other peoples work? The person that did the original work is already forgotten and credit is given to others, how fair is that?
As for the apple tree analogy, would it not be more fitting to just use a tool that already exists? Is that not on a lower branch?
I think this is the single biggest problem on NGU. I do not wish to discourage people from learning to program but you really should not publish work that contains absolutely zero new content, keep it to yourself. If you had even put a minor new hack into your tool I would give you nothing but praise, but you did not, you only copied others work.
There is a big difference in including publicly known hacks in a tool that introduces something new and making a tool that is made of ONLY publicly known hacks. The latter should NEVER be publicly released. I hope this explains why I groaned your topic.
As for the apple tree analogy, would it not be more fitting to just use a tool that already exists? Is that not on a lower branch?
I think this is the single biggest problem on NGU. I do not wish to discourage people from learning to program but you really should not publish work that contains absolutely zero new content, keep it to yourself. If you had even put a minor new hack into your tool I would give you nothing but praise, but you did not, you only copied others work.
There is a big difference in including publicly known hacks in a tool that introduces something new and making a tool that is made of ONLY publicly known hacks. The latter should NEVER be publicly released. I hope this explains why I groaned your topic.
bro you always talk a lot lool
The following user thanked wajdi9 for this useful post:
01-21-2015, 10:43 AM
#14
wajdi9
Space Ninja
Originally posted by 04jberry
Destiny 1.08 RTM
Description: So i used NelsonHacks Tool to get the offsets and the devcomponents dll made it look
a bit smart and idiot proof.
The CID changer has a maximum and minimum of 32 characters so you can just hold 0.
I made the 1 shot kill x10 x20 x999 so when you click either one the others disable so you may
change and they won't all be checked.
if anyone like this tool and would like me to add the visions in just send me a message and ill add em.
You must login or register to view this content.
Tool: You must login or register to view this content.
Source: You must login or register to view this content.
Description: So i used NelsonHacks Tool to get the offsets and the devcomponents dll made it look
a bit smart and idiot proof.
The CID changer has a maximum and minimum of 32 characters so you can just hold 0.
I made the 1 shot kill x10 x20 x999 so when you click either one the others disable so you may
change and they won't all be checked.
if anyone like this tool and would like me to add the visions in just send me a message and ill add em.
You must login or register to view this content.
Tool: You must login or register to view this content.
Source: You must login or register to view this content.
Nice tool Jordan i think if you add anti ban or something to protect you while you are modding then your tool will be the best. keep up the great work
01-21-2015, 05:16 PM
#17
PseudoAnonymous
I can spell
01-21-2015, 07:08 PM
#18
XxUnkn0wnxX
F4LLEN ANG3L
The following user thanked XxUnkn0wnxX for this useful post:
01-21-2015, 10:43 PM
#19
Loxy
< ^ > < ^ >
Originally posted by PseudoAnonymous
Does anyone know how Bungie implements the bans? I'm thinking of activating the PvE godmode to defeat Atheon. Does Bungie rely more on reporting or do they have some sort of checks? (Please don't tell me about them detecting CFW, I know all of that already)
Lol why risk the chance it's not hard really if you have a decent fire team that know what there doing. I done it 3 times on hard for this week and i will try again next week till i get my vex mythoclast :troll:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
