Staredit Network

Use a Binary/Hex converter like this one to get your hex value (in your case is is 80), then use MemCalc to get the StarForge trigger to change the 4th byte of -29426 for P8 to 80.

Addition-

I have some questions of my own. I made a Probalisk (Ultralisk that looks like a Probe) but he's moving at like 1 pixel/second after converting from Iscript (it wasn't moving at all) to Flingy MoveControls. What's the offset for Flingy Speed? Can it be modified to correct my Probalisks problem? Also, the attack is altered and the probe just sits about 32 pixels from its target and doesn't claw it to death; I tried altering subunit range to read 0 and unit size to subtract 2 (Large -1 = Medium, Medium -1 = Small) but neither process made him attack or get closer to his target. Help?

I tried both Hex and Dec. and neither are working (Trying to get Dropship to stay on ground as if it were a groudn unit)

Why would you set the target acquisition range to 0?
I think the problem is in the unit AI's, because, as you may have noticed, peons act differently in regards to auto-attack, retaliation, etc.
As for speed, my best guess would be that it has something to do with the fact that Ultralisk uses iscript while Probe uses flingy(though I'm not sure about Ultralisk), but I don't see why that would make any difference, since flingy is still about sprites, so...
As DTBK said, the attack problem is with the AI's. Atleast, I'm pretty sure it is.

Because the Probe Subunit Attack range is 0, which would make the Probalisk sit there until I order it to attack.


You are correct, it does matter. However after switching to Flingy MovementType, the Ultralisk is directed to use it's speed and accel values from the Flingy.dat, which are both 1. StarCraft usually ups these "1" values to their actual amounts during the Ultralisk Iscript execution, which is now disabled.


The problem is not with AI's, it is with the attack range being less than the physical buffer around the Ultralisk, because the Probe flingy makes the unit smaller, whereas the buffer is remaining the same. He can't touch other unts at all.

To make the dropship act like a ground unit there is more then one thing you need to edit. The movement flags you edited just have to deal with what terrain it can go over. So to test if what you have changed worked, try and make a dropship move over a cliff, water or some other unwalkable terrain. After that you need to edit the units animation level to something like 4 so the sprite is drawn at the proper height, ground level (4) as opposed to air(16). I'm not sure what you need to put in for the triggers but if you look around you should find it.

Just so you guys know, your computer comes with a hex/decimal converter. Open your calc and switch it to "scientific", if you want hex->decimal, first switch it to hex, then type the # in, and then switch it to decimal, and walah. Works the same in reverse.

Can someone do that for me? I'm technically challenged when it comes to that =\

I have a question, is it possible that you could add in a EX. Trigger in memcalc telling what the deaths part means, cuz for some i cant figure out how to change it -.-

hey, ive been doing basic triggers of this now and i need to know something. What would i edit to change the range of distription web. all these confusing names from the memcal are confusing me on which to use...

like how far you can cast it

it sais that it cant handle splices or whatever that is......

You can't do it, it's a p11 one.

Memcalc - Unit.dat->animation height->terran dropship

I have just one question.
I know that if you change the units attack range, the AI still makes them run closer to shoot.
What happens if you make the actual attack range less than the AI scripts range.

I'd test myself but am on a mac at the moment.

Oh crap, from battle.net forums 'the impossible has been found' topic -


JohnDS

34. Re: The impossible has been found. Read. | 8/4/2005 2:57:20 AM GMTDT

Thanks for the "heads up". I'll ask the developers to take a look into it.

urmom,

I know you've gotten to the StarForge Trigger Converter step, but I'm writing the whole modding process out for everybody else who isn't in your position yet. Your question is answered at the end of this post.

Editing offset "6BC58C - Maximum Range" in the Weapons.dat for object "101 - Disruption Web" with MemCalc Easy Mode returns the following output:


The default max range of disruption web is 18. To set a new range, pick a number then convert it to hexadecimal using a converter like this one to turn that number into hex. EX. Say you want a range of 40, a little over twice the default range, then you would type in 40 and get 28 in hex.

Usually one would use the MemCalc StarForge Trigger Converter so that it reads as following:


HOWEVER, as urmom saw, MemCalc returns the "spliced value" error. This usually means that the longs are crossing across eachother, but in this case they actually aren't (DT, you better fix that ).

We know what we want to end result to be: 28 00 00 00 deaths of unit -29277 for player 8. The resulting trigger can be done by hand:

SetDeaths(P8, SetTo, 28, -29277);

Using SetTo sets the other 3 bytes in the long to 00, but that's alright in this case because all 4 bytes ("00 00 00 00") are used for the "Weapon Max Range" of "101 - Disruption Web." Simply put that action into your map and Distruption Web should then fire at double range. Remember to assign the Disruption Web as a weapon for a unit, cause I'm not sure this will double the range of the ability - just the weapon, which isn't an actual StarCraft weapon, but it can be used as one. Good luck.

I posted on Battle.net in that thread with the following message to JohnDS, the Blizzard employee who posted the aformentioned message:



Hopefully this will stop any lightly-made and incorrect decisions Blizzard can take right now. I'm looking out for you guys; this is a valuable technology that will make the remainder of my summer less boring.

This is great and all, but this is the second big discovery that has come to light from the staredit community within the last few months... Either blizzard won't care, or they might actually do something more drastic this time. How am I supposed to know though? Hell, they might even make a patch to make it work on macs.

I'm waiting for JohnDS to reply to my message. He or another representative will probably tell us what Blizzard decides to do; I'll post that message here for everyone when it is available.

Tearshed- Thank you for bringing this to our attention.

Thanks for telling blizzard our side of the story and the good points of these triggers(of course the goods points are the only points)

I made a somewhat "babbly" reply, I'm a bit tired. But what I posted is true, I hope they help make the EUD trigs, rather than hinder and/or eliminate them. That'd be a shame...

Wait... so can you use these triggers to tell a location "move X pixels to the right", or "stretch X pixels to the right", or can you only do things along the lines of "stretch right side to pixel X"?