• Content count

  • Joined

  • Last visited

Community Reputation

18 Good

About Mjjstral

  • Rank
    Lance Corporal

Contact Methods

Profile Information

  • Gender
  • Location
  • Interests
    philosophy, border science, science fiction

Command & Conquer Profile

  • Favourite C&C
    Kanes Wrath

Recent Profile Visitors

1,015 profile views
  1. You could make a simple batch script with/and/or use of some regex replacements.
  2. Of course we can have a very reliable three-sigma-rule heuristic (99.7%) based set of numbers if we wish. And for my argumentation a lower conservative estimation would always be valid. Let's not spam this forum with this, better write pm's if you need further explanations
  3. See Bayes' theorem Misunderstanding from your side. Every map script of course affects the ram. By saying it this way I just wanted to point out that it is not a permanent file related change or something. The thing is this exploit is so damn simple. You just need to activate the camera letterbox mode and exit the map, done... I'm not sure but maybe this even works if you exit the map during campaign camera letterbox mode parts. Then you don't even need this map. Also there are many custom maps played in mp (td,aod maps especiallly) with cinematic like intros, just exit the game during that phase and boom you also have that same exploit enabled. Enter another mp game after that and unintentionally zoom out more...
  4. See the relation between SteamDBCurrentPlayer and CnCOnlineCurrentPlayers. Reliable ? Not sure but at least we can assume that most players use singleplayer (it has always been in rts games like that, a rts game dev once told me). Don't nail me on statements like that. It's clear that this is a really rough guess and people can make their own opinion (but I'm almost sure more people use the origin+retail then steam version). Sorry it was not in any way my intention to offend you in any way ! Yes but that doesn't matter because the steamdb current player number which I used for my rough guess also coreelates to the same peak times. For singleplayer players as I stated. I myself could't play the BFME games (in sp of course) without more zoom out. Also for CNC4 it is really great to have such an amazingly better overview. You should test it, it's a complete game changer to the good. And as you see this map exploit also supports RA3 uprising which is as you know a pure singleplayer game. I'm sorry that I caused so much trouble. I was never into all that multiplayer stuff but now I see the point and the problems for that regarding the strict fair play rules. Still in my opinion more people benefit from it then not. This map has been a part of metamod already quite some time, I just thought to bring it to the people as a seperate thing.
  5. I mean there are at least 15 sp players for each mp player. That makes my argument even more valid because then there are maybe even 30 sp players for each mp player (you can actually see the number of cnc-online players here, hence my deduction). So if we deal with this in a philanthropic way and use utilitarianism logic, this exploit should be public for the benefit of the majority of players.
  6. Well my intentionts with this were entirely good. There are clearly more singleplayer players that benefit from this then multiplayer players using it as an advantage especially for the BFME games (utilitarianism). If we look at steamdb and cnc-online we can guess a ration for sp:mp of 1:15. And for the multiplayer part the thing is that you can easily detect if someone uses it with help of the replay (from the "eyes of player mode"). So in the end this is actually a good filter to detect all "dishonest" people and let them get banned if necessary. So as all things in live this exploit has it's polarity. Nuclear fission for instance can be used for good to produce power or for bad to produce weapons. But is that a reason to completely ban the knowledge of nuclear fission ? I unintentionally found other even undetectable and by far more heavy exploits that work in multiplayer too but these I will never make public because the singleplayer benefit is just to slim.
  7. I posted it 7 times (for each game this thing works) because I consider this to be quite a beneficial game changer that every player should make use of. Sage engine games and their max zoom out have always been a problem in my eyes. For C&C Generals we could fix the zoom easily in the gamedata.ini. But that didn't work for most games after Generals. Now we have an easy modless solution that even works for multiplayer. It's a huge coincidence that I even found this bug, unfortunately 10 years too late for most former players lol.
  8. You can spawn the monetary compensation dummy object quite hidden in the down-left corner so players won't notice. It's a lua oneliner if you have the GetTeamName function: ExecuteAction("CREATE_OBJECT","MoneyDummy",GetTeamName(self),"0.00,0.00,0.00",0)
  9. It's ridiculous, they removed my posts about this from the gamereplays forums. Do people really consider this exploit to be an unfair advantage ? It's just a map....
  10. Ok I've added Lord of the Rings The Battle for Middle-earth 1 as well as Command and Conquer Red Alert 3 Uprising. Unfortunately it doesn't work for vanilla red alert 3, sorry.
  11. I have some origin keys left. PM me if you want one: Sim City 2000 Special Edition (4 keys) Battlefield 3 Limited Dead Space Dragon Age Origins Zumas Revenge This guy also gives away some free keys for origin and steam although most keys are gone already.
  12. The advantage of this exploit is the modlessness and therefore multiplayer compatibility. This exact exploit is only possible via loading a map once. Via mod I came up with similiar solutions to have better zoom (3 different ways in meta mod) but all these always require user input either via player power button or via adjusting the autoconfig file. Your're right I didn't test it for BFME 1. I need to install it first.
  13. This is a sage engine bug exploit map pack for all sage games post C&C Generals/ZeroHour. After loading the map once, you will have limitless zoom for all maps you start afterwards. In skirmish and even in multiplayer ! The map hereby only deals as an agent/injector to trigger the engine bug exploit. So technically speaking it is a map but actually it's more a mod without actual mod. The changes are not permanent (only RAM related) and everything will be back to normal if you restart the game. The following games are supported with this pack: Command and Conquer 3 Tiberium Wars Command and Conquer 3 Kane's Wrath Command and Conquer Red Alert 3 Uprising Command and Conquer 4 Lord of the Rings The Battle for Middle-earth 1 Lord of the Rings The Battle for Middle-earth 2 Lord of the Rings The Battle for Middle-earth 2 - Rise of the Witch-King Unfortunately it doesn't work for: Command and Conquer Generals Command and Conquer Generals Zero Hour Command and Conquer Red Alert 3 How does this even work ? It uses a map script that triggers an engine exploit by not reseting a special camera state. In addition the map render distance gets set 3 times higher to avoid black borders for high zooms. Installation: Put the map folder "!RemoveZoomLimits" for the respective game into this folder (for your case): C:\Users\>Username<\AppData\Roaming\>GameName<\Maps Entire maps viewable !
  14. A lazy workaround: Growth Accelerators fire weapon on same type and same team (excluded self) in a narrow range around them to eliminate duplicates with a special death type. Use a random delay between shots. Duplicates create an object on that special death type that creates the monetary compensation. If it has to do with the tiberium field you could replace it with an unbugged version via lua easily on map start automatically (I can explain if needed).
  15. The name of the parameters doesn't matter, what matters is the actual data type that lies behind them. That means you can rename self to whatever you like. Self is a lua table type, spySelf must also be a lua table, as all ScriptEvents given object arguments are. Everything that follows is very likely a string. You can test what lies behind these parameters when you display arg[3] and arg[4] ... To test the type just display type(arg[3]). You can also define the whole function header with three dots like that: function OnExampleSpyMoving(...) That doesn't limit the number of arguments if you don't know how many you get, but then you are limited to access them only with arg[NumberOfArgument]. Hope that helps.