62 replies to this topic

[Kira Onime]

Not sure why a list is necessary.

[EvilCow]

Gagis, on 28 May 2015 - 06:30 AM, said:

I am using both of these. I am running MWO on Linux using Wine, which has a built-in debugger and runs windows games by wrapping directx and other windows dll:s to the native opengl and other functions in the Linux OS.

Banning #3 and #4 means people won't be able to play your game on Linux or Mac, and is thus seldom done, and when they are banned, the community backslash is usually huge.

Nope, Wine does not attach to processes and does not wrap DirectX DLLs, it implements DirectX interfaces over OpenGL. They can decide to whitelist it if they want, so it does not matter.

[DjPush]

I think Macros are a cheat. That's just me. It gives you an un-natural edge over others. I'm sorry, but you should only be able to fire as fast as you can push a button. Having a computer fire for you is a cheat to me.

[Dino Might]

DjPush, on 28 May 2015 - 07:06 AM, said:

I think Macros are a cheat. That's just me. It gives you an un-natural edge over others. I'm sorry, but you should only be able to fire as fast as you can push a button. Having a computer fire for you is a cheat to me.

I'm not meaning to poke fun at you personally, but you have to see the comedy in this statement.

Edited by Dino Might, 28 May 2015 - 07:09 AM.

[Gagis]

Dino Might, on 28 May 2015 - 07:09 AM, said:

I'm not meaning to poke fun at you personally, but you have to see the comedy in this statement.

I don't see the joke. The use of macros and other automation is banned in a lot of games.

I understand why they are not banned in MWO, but its not an entirely outrageous or in any way comical opinion to expect them to be.

[Mycrus]

Ts3 because in game voip

[Mad Porthos]

I think the comedic irony of being opposed to Macros and having a computeer fire faster than you can push a button comes from the fact that all of this is happening on a computer and that is the whole purpose of the computer, to automate the "pushing of a button" so it can happen faster and more accurately/efficiently than a human pushing a button. Further irony comes from the fact that what we are simulating is not even an analog experience... the simulated mechs simulated targeting/fire control computers most definitely could "fire" for the pilot hundreds even thousands of times per second, heck... they already do for AMS, managing to accurately hit incoming missiles. They fire machine guns fast too. No reason for cooldown EXCEPT mechanical limitations, not digital/electronic at all. So if they have set ac2 so it has a cooldown that is so short that it could fire again faster than you can click, I AM SURE the "simulated computer" could fire it, rather than waiting on the pilots stubby fingers to finish going clickety click... little different than a machine gun really.
It is on PGI to update the control and firing options if they do not want macros, making it so that either continually held buttons are "polled" more often than .5 sec - set by pilot to some range of numbers, so that an ac2 can be fired at its true available ROF - along with the faster buildup of heat that entails. Since they deemed that work/feature not a priority, they are content to allow extant macros software to fill the gap for those who want to squeeze every drop of dps out of them, using macros. Macros which DO NOT ALLOW those ac2's to actually be fired any faster than is possible in the game engine, instead merely allowing consistent "rapid clicking" which one might not be otherwise personally be capable of due to arthritis,carpal tunnel syndrome, being a old person or flat out missing digits and hand mobility. For those without these issues though, WHAT ABOUT THEM?!@!?
Seriously? You want them to get that stuff, carpal tunnel, arthritis, etc? Just cause some might feel their badge of honor as a 360noscopeheadshot survivor is a wickedly advanced mouse hand trigger callus, accompanied by tingly carpal tunnel complications does not mean the rest of us want to walk that road, thank you very much.

Edited by Mad Porthos, 28 May 2015 - 07:53 AM.

[Tombstoner]

Dino Might, on 28 May 2015 - 07:09 AM, said:

I'm not meaning to poke fun at you personally, but you have to see the comedy in this statement.

Except that macros can automate your rate of fire, in-effect electronically preventing you from jamming your ultra ac's when you go full auto.

Mad Porthos, on 28 May 2015 - 07:47 AM, said:

I think the comedic irony of being opposed to Macros and having a computeer fire faster than you can push a button comes from the fact that all of this is happening on a computer and that is the whole purpose of the computer, to automate the "pushing of a button" so it can happen faster and more accurately/efficiently than a human pushing a button. Further irony comes from the fact that what we are simulating is not even an analog experience... the simulated mechs simulated targeting/fire control computers most definitely could "fire" for the pilot hundreds even thousands of times per second, heck... they already do for AMS, managing to accurately hit incoming missiles. They fire machine guns fast too. No reason for cooldown EXCEPT mechanical limitations, not digital/electronic at all. So if they have set ac2 so it has a cooldown that is so short that it could fire again faster than you can click, I AM SURE the "simulated computer" could fire it, rather than waiting on the pilots stubby fingers to finish going clickety click... little different than a machine gun really.
It is on PGI to update the control and firing options if they do not want macros, making it so that either continually held buttons are "polled" more often than .5 sec - set by pilot to some range of numbers, so that an ac2 can be fired at its true available ROF - along with the faster buildup of heat that entails. Since they deemed that work/feature not a priority, they are content to allow extant macros software to fill the gap for those who want to squeeze every drop of dps out of them, using macros. Macros which DO NOT ALLOW those ac2's to actually be fired any faster than is possible in the game engine, instead merely allowing consistent "rapid clicking" which one might not be otherwise personally be capable of due to arthritis,carpal tunnel syndrome, being a old person or flat out missing digits and hand mobility. For those without these issues though, WHAT ABOUT THEM?!@!?
Seriously? You want them to get that stuff, carpal tunnel, arthritis, etc? Just cause some might feel their badge of honor as a 360noscopeheadshot survivor is a wickedly advanced mouse hand trigger callus, accompanied by tingly carpal tunnel complications does not mean the rest of us want to walk that road, thank you very much.

Its about using macros to prevent you from triggering the jamming mechanic. you maximize damage with no chance of jamming. id call that a cheat.

[Xenon Codex]

Tombstoner, on 28 May 2015 - 08:19 AM, said:

Except that macros can automate your rate of fire, in-effect electronically preventing you from jamming your ultra ac's when you go full auto.


Its about using macros to prevent you from triggering the jamming mechanic. you maximize damage with no chance of jamming. id call that a cheat.

Not anymore. They changed the UAC mechanic a while back so holding the fire button doesn't cause jams. It's only double-clicking on purpose that causes jams. So no need for a macro.

[Almond Brown]

If a list is wanted or needed, how about someone take that List of 64 and update it with Team affiliation and or Pug status. Would be good to see if Teams, vs Solo's are the main culprits on the whole Hacking scenario...

I would bet that Team players/members would make up the vast majority...

[Mad Porthos]

As Xenon Codex I think pointed out - no, it does not maximize your ROF without jamming because you can literally just hold the fire button down and you do the same thing, fire and then after a 1.66 sec cooldown, fire again w out jamming. If a macro tried to fire any faster than that, it would be a double tap making it have a chance of jamming, just the same as anyone without the macro. This is not new behaviour for the uac5 either, it has been this way for an extended period of time, years even by this point since they 'normalized' the autocannons. if a macro is set at a rate that will not trigger jamming, then the uac5 is firing as an AC5 that is a ton overweight, no advantage gained and it even takes more slots.
By and large, this incorrect claim that a macro allows a jam free uac5 and the belief that it is unfair to have ac2 firing as fast as its cooldown allows are the primary fallacies that keep being dragged out in macros conversations and cheating debates.

Edited by Mad Porthos, 28 May 2015 - 10:18 AM.

[Khobai]

Quote

I think Macros are a cheat. That's just me. It gives you an un-natural edge over others. I'm sorry, but you should only be able to fire as fast as you can push a button. Having a computer fire for you is a cheat to me.

Macros arnt really a cheat. Macros are however indicative of poor weapon mechanics.

For example, If TAG had an on/off toggle there would be no need to macro TAG to always be on.

Same goes for UACs. If you could fire the double shot by holding down the mouse button there would be no need to macro it.

And gauss chargeup... another bad mechanic that gets macrod.

Players primarily use macros to avoid the frustration of bad weapon mechanics that shouldnt exist in the first place. Not to gain an advantage over others.

The reason why PGI allows macros is because theyre aware of their shoddy weapon mechanics. Since all players have equal access to macros there is no inherent advantage to using macros. If you choose not to use macros thats your choice, but dont claim youre at a disadvantage because of that choice.

Edited by Khobai, 28 May 2015 - 12:44 PM.

[Johnny Z]

I will say this right now as a favour. I suggest all players play the game as is without modifying it at all. Many game alterations that are ok now may not be ok later. Then its tough to adjust to playing with out the crutches then players get banned.

This has happened in other games and no reason to think it couldnt happen with this game. Just a heads up.

[Mystere]

Damn! It's already 2015, or 3 or so years into MWO, and people are still complaining about macros, even though time and time again they have been pointed to this several times? Hot damn!

[Xetelian]

DjPush, on 28 May 2015 - 07:06 AM, said:

I think Macros are a cheat. That's just me. It gives you an un-natural edge over others. I'm sorry, but you should only be able to fire as fast as you can push a button. Having a computer fire for you is a cheat to me.

Agreed. I especially despise the Gauss firing macro, I think it is a pretty significant advantage.

[AlphaToaster]

I'm surprised they allow SweetFX since it sounds like it can be used to make mechs easier to see. I notice a lot of the maps are really dark, the mechs are shadowy, and the visiblity is really terrible, even with the alternative visions. I can pump up gamma, but then it washes everything out and blinds me on bright maps.

It would be a sad state of the game, if 3rd party software were needed to clean up the visuals rather than those changes being baked into the engine.

Is this game still a beta or something?

[Khobai]

Quote

I'm surprised they allow SweetFX since it sounds like it can be used to make mechs easier to see.

not really. it makes the game look more crisp and vibrant. but it doesnt really make mechs any easier to see.

[LordNothing]

DjPush, on 28 May 2015 - 07:06 AM, said:

I think Macros are a cheat. That's just me. It gives you an un-natural edge over others. I'm sorry, but you should only be able to fire as fast as you can push a button. Having a computer fire for you is a cheat to me.

one thing you can do is keep your gauss cycling so you just have to tap a button to fire (no i wont tell you how). if you have 2 you can alternate them so there is always a gauss ready to fire. if you have a high end joystick (anything ch or thrustmaster) then those behaviors are scriptable within the stock profile software. you can also cycle weapon groups with one button, so if you have a laser vomit boat you can fire 3 lasers at a time by hitting one button.

i do not do these things because i consider it cheating, i use the software strictly for organization (so i dont have to remember my mappings, i just map to defaults so even with a fresh instal everything is where i want it, and to be fair it probibly adds some latency in inputs over mapping ingame and all my firing controls are on the mouse). though in some situation input hacks are required, for example the disabled. hard to play mechwarrior with one hand without macros. id hate to be here for that lawsuit.

Edited by LordNothing, 28 May 2015 - 04:02 PM.

[LORD TSARKON]

VPNs... I know they are not a banned Program but is there an official PGI statement on them? A Friend of mine thinks the VPNs might have caused some of the PErm bans in the recent Ban Wave (no.. he was not banned.. but someone from his Unit was)...

I told him RUss only said Aimbots/Wall hacks were responsible for the current Ban... but I guess you can use VPNs to throttle your network and cause Latency shield armor,ect....

Anyways.. is there any word from PGI about that?

[Mechwarrior Buddah]

KiraOnime, on 28 May 2015 - 06:46 AM, said:

Not sure why a list is necessary.

So you dont get banned for using something thats illegal but you didnt know it was illegal because they didnt tell you what was