W3S Auto updater

War3:Source > General Discussion > War3: Source - General Discussion > W3S Auto updater

Poll

Question:

Custom compiled smx handling method (Voting closed: July 03, 2014, 03:23:08 PM)

use a separate folder for custom compiled .smx	3 (25%)
use a ini file to specify which files not to update	6 (50%)
check plugin's build number to see if is a jenkins build or custom build	3 (25%)

Total Voters: 12

Pages: 1 [2]

« previous next »

Author

Topic: W3S Auto updater (Read 1132 times)

Remy Lebeau

Sr. Member

Posts: 405

Re: W3S Auto updater

« Reply #25 on: June 30, 2014, 06:20:28 PM »

I'm flabbergasted.... A simple search on war3evo forums for the url of this thread, and voila...

I hardly know what to say ... At what point of creating that request over at war3evo did El Diablo think it would fly? Like we don't already know who the major players in w3s development are, because a ton of random newbie's posting votes wouldn't seem suspicious.

But even worse than that is the mentality that seeks to have the development progress in the direction he wants at whatever cost. Charitably, I'm going to put this down to a brain snap, and assume it was just one of those things that seemed like a good idea at the time.


	Logged

Necavi

Sr. Member

Posts: 498

Re: W3S Auto updater

« Reply #26 on: June 30, 2014, 08:09:12 PM »

Quote

20:02 - -W3E- El Diablo: im guessing that Ownz didn't like my use of community power Sad

20:02 - Necavi: Is that what you're calling it?
20:03 - -W3E- El Diablo: perssuaion?
20:03 - -W3E- El Diablo: im a bad speller
20:03 - Necavi: Uhhh...yeah....
20:03 - -W3E- El Diablo: its more like commuinty persuassion
20:03 - Necavi: No, it is offerring rewards to rig a vote in your favour
20:03 - -W3E- El Diablo: I didn't think I'd get it past him.. if it was a ton of votes really fast
20:04 - -W3E- El Diablo: I was curious to see if it would work.
20:06 - Necavi: It was pretty damn obvious that something was up, I just didn't care enough to post, and I figured Ownz would just do whatever he wanted in the end anyway
20:10 - -W3E- El Diablo: Well.. War3Source needs a little more activity anyhow .. what better way to spice it up ?
20:10 - Necavi: With actual content rather than spam from your forums
20:11 - -W3E- El Diablo: Are you mad?
20:12 - -W3E- El Diablo: I don't expect mine to go thru anyhow.. I had the lesser votes in the first place.
20:13 - -W3E- El Diablo: I already knew by the time there was numerious votes that you guys would figure it was a fudge votes.
20:13 - Necavi: I don't really care enough to be mad, but I am very annoyed that you actually are deluded enough to think you're helping the community by paying members of your server to come post to try to get your way
20:15 - -W3E- El Diablo: I didn't think mine would go through.. but I was just a little curious if it would even make it... like 1% chance. Platinum isn't real currency. It is game currency.


	Logged

joshtrav

Newbie

Posts: 6

Re: W3S Auto updater

« Reply #27 on: July 02, 2014, 09:11:15 PM »

I got a lol out of the dude begging his community to vote.

But on topic,

I guess my idea would be to have a base update plugin that is updated no matter the case. It would have hashes of all the current builds, or something of that nature. If users plugin hash/version, w/e, is in the list, go ahead and update, otherwise don't.

But if I had choose between the remaining I would say its a split between Ownz/Necavi. The ini is pretty, well, you know what I want to say there...

Either way, we don't use war3source but from a dev standpoint I thought I would chime in since the thread gave me a good chuckle.


	Logged

Revan

Sr. Member

Posts: 437

Re: W3S Auto updater

« Reply #28 on: July 10, 2014, 04:55:53 AM »

Quote from: joshtrav on July 02, 2014, 09:11:15 PM

I guess my idea would be to have a base update plugin that is updated no matter the case. It would have hashes of all the current builds, or something of that nature. If users plugin hash/version, w/e, is in the list, go ahead and update, otherwise don't.

Yup, I also proposed something like that - the problem is that the hash changes every time the plugin is compiled(an alternative is to compute the hash only from the .code section - that should stay the same across different compiles). Plugin version sounds like a nice way too!


	Logged

#war3source on gamesurge

Pages: 1 [2]

« previous next »

Jump to: