|
|
Hi please keep the replies on topic with OP, users will be infracted for spam if this rule is not adhered to.
Nice release Greg, always useful having these sorts of threads, reminds me of one I released for OSRS a couple years back. It's always cool to share information like this instead of those that just keep it to themselves.
because we don't want it to be open source right now. we've already released a lot of the valuable information we've collected while developing dusk, in contrast to what you did for stronghold.Originally Posted by Scu11
dang why would you wanna hinder the community that helped you become the programmer you are today?
do you undervalue the other members of this community so much that you wouldnt share your code with them?
loads of people could profit off of dusk being opensource
it doesn't make sense to me that you wouldn't do the best for the community you learned so much from, especially in this scenario
nobody else needs to spend so much time on such a tedious task of building their on 667 if you've already done it for them, so sharing it would be rational, u know?
do i have to paste the chatlogs of me giving u and greg pages of info from 667 lol? not to mention the 667 releases ive posted on this site:we've already released a lot of the valuable information we've collected while developing dusk, in contrast to what you did for stronghold.
[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]
i release everything i can while i'm working on somethingdang why would you wanna hinder the community that helped you become the programmer you are today?
do you undervalue the other members of this community so much that you wouldnt share your code with them?
loads of people could profit off of dusk being opensource
it doesn't make sense to me that you wouldn't do the best for the community you learned so much from, especially in this scenario
nobody else needs to spend so much time on such a tedious task of building their on 667 if you've already done it for them, so sharing it would be rational, u know?
the main reasons that would make me not release anything is
1) it affects my income
2) it'll generate more competition
regardless of that, i released redrune666. while working on dusk.
redrune666 was being used by a another project while i was working on mine, but i thrive on competition.
follow?
Thanks for the release Greg.
No one is under any obligation to release anything.
(Tyluur)
I get why Scu is mad since you attacked him for no reason, but rsps users are 'real people' with 'real problems'. Not sure he meant it to come off quite so poorly.
these are good releases, but they're from 2018. you've done a lot since 2018 that could've been released.
sharing chat logs would be an odd thing to do, weird to say that. it's public information that we've gone back and forth with info.
i release everything i can while i'm working on something
sounds a bit selfish that and doesn't really address any of the same points you posed to me about releasing stuff
i forgot that a list of tree IDs is of comparable importance to libraries that are downloaded thousands of times by actual developers in the field
> i release everything i can while i'm working on something.
sounds a bit selfish that and doesn't really address any of the same points you posed to me about releasing stuff
why dont u?
| « 915 Lists | Equip Sounds(614) updated » |
| Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |
| Tags for this Thread |
