Noted. I appreciate it still being on your todo list - NPC loadouts are nothing short of a pain in the ass, and this would save hours of work and create a much more dynamic PvE experience in allowing a much greater range of weapon / equipment combos to be encountered.

Awesome! The second offset controls exactly what I’m looking for - it controls the sensitivity for which nudge_force is used, so raising it a little stops excessive auto-dodging while still preserving proper AI strafing and docking alignment. Many thanks!

Timmy51m wrote:
I don’t know if it well help, but in one of the story missions, one of the early ones, willard research station gets attacked by the rheinlanders. There’s a set of bombers that you have to destroy that are attacking the battleship, they appear to ignore everything else. Might be something in their that helps you out.

Since it’s in story mode, it’s probably coded in the mission script that they attack the capships and ignore the fighters.

thanks works a treat was glad to see the back of that

Read 1 again. Basically:

attack_preference = invalid ship type, whatever, whatever

is the same as:

attack_preference = anything, 5000, GUNS | GUIDED | UNGUIDED | TORPEDO

FF’s dead true… when testing things for extended periods of time… one can start to notice things they would otherwise plain miss…

Pain in the ass if you ask me… ignorance is bliss 8-) at least then you can claim…“ive never seen it”…

Just like you haven’t played in two years, I haven’t looked at vanilla code in almost five. 😉

I’d play around with the RandomMissions missile thing more, but I removed (read: broke) RM functionality in Flak so long ago I need to jump back on a vanilla codebase to look further. I’ll play around with it tomorrow when I get sick of doing of doing homework.

Here’s another approach, removing the item altogether (so make it 00000FE0 to remove the cloak).

freelancer.exe 0E6F1E 00001FE0 = equipment types shown on wireframe ~adoxa 1 - CELightEquip 2 - CEAttachedFX 20 - CEMineDropper 40 - CECounterMeasureDropper 80 - CEGun 100 - CEShield 200 - CEShieldGenerator 400 - CEThruster 800 - CECargoPod 1000 - CECloakingDevice 10000 - CECargo 20000 - CEEngine 40000 - CEPower 80000 - CEScanner 100000 - CETractor 200000 - CERepairDroid 400000 - CEInternalFX 800000 - CETradeLaneEquip 1000000 - CEArmor 1FE0 - CAttachedEquip 1FE3 - CExternalEquip 1FF0000 - CInternalEquip

Cool, that’s wicked useful. Thanks adoxa.

OK, I see what happened. The previous hex editor I used would automatically overwrite the block that I was typing in. Tiny Hexer you either have to highlight the block before you type, or hit delete to clear the existing entry.

My edit now reads:
0xA490 5DC2 0800 6681 7CE4 045A 1374 E291 EBCE

I’ll give that a try. Thanks again Adoxa.

Agreed, the best solution would probably be to have FLHook spawn an NPC of the same faction, archetype and loadout on the other side of the hole.

That said, somewhere in an NPC’s info there should be a jumper flag. If you use mission scripting to set the jumper flag on a mission-spawned NPC, that NPC will jump with you when you leave the system (but only when you switch systems, and I don’t think it matters if the NPC itself used the gate or not - if another player is watching this happen, the mission-spawned NPCs simply disappear from the previous system and jump into the new system via the gate the player used). Thus, perhaps it’d be possible to set the jumper flag to true for all NPCs within a certain distance to a player?

Adoxa, you’re seriously the man. You have no idea (well, actually, you probably do 😛 ) how useful these hacks have been. I feel guilty making so many requests, but both you and w0dk4 have put a lot of really useful stuff up on that list over the past month alone.

I could probably do better on my end maintaining that list and getting the Wiki up to speed; I’ll do some of that before leaving this weekend for the 4th. Thanks again! 😄

Okay, I probably should have done this with the other patch. It adjusts the offsets to work with the Follow structure, but even if it works, they might all follow at the (0,0,0) vector, so a plugin would be needed for that.

6CE24: 14->4C
875BC: 18->50
875C2: 1C->54

Hopefully that’s all that’s required.

Excellent, thanks Adoxa. I can’t test it right now as I’m away from home and my netbook can not run Freelancer (I get the text corruption bug and crashes on this chipset), but I have a feeling it will do the trick. 😄

For those curious, yes, M0tah’s FLHook in 88 Flak has native support for using F3 docking on players - as soon as the game would actually try to dock you and cause a crash, FLHook steps in and runs the mobile docking code (the same as using the /dock command currently in play). Since this code has actually been active all along, any mod using his FLHook solution will immediately benefit from this hack.

The issue with using type = STATION on players is not just the handling, but also some other things. For example, players show up as “New Tokyo System, Sector B3” when targeted (instead of “Rogues - Deathflier” like normal players), and there are also issues with the way AI target and attack these players (in multiplayer, AI only properly attack FIGHTER and FREIGHTER types - anything else they generally ignore, try it yourself). Thus, enabling F3 docking on type = FREIGHTER is simply the easiest solution.

Thanks again! 😄

Thx! Very useful for station’s subtargets

yeah, we get players who like to fly the big transports by choosing a waypoint and hitting F2 and then busy themselves with other things. I prefer to fly.

ruhroh, thread is being threatened with derailment

sorry…

From my experimentation:
The first two edits define left and right, you can have one or the other, of course it’ll only work one way unless you have both.

The other two… Well, if you don’t have both and you’ve edited the first two it ctds, so I got no clue what they do by themselves. xD

I wouldn’t go any deeper into it because it’s all just letters and numbers to me. :<

So I noticed some peculiar behavior and was hoping someone would be able to shed light on this.

PhySys::GetCollisions seems to return all collision events, even those that involve beam weapons. Oddly, though, it doesn’t put a CBeam pointer in the second slot, instead it puts a pointer to what appears to be garbage. All I could notice was that the pointer would point to another pointer which would point to another pointer and so on until the last pointer goes to 0x0. All data around those pointers is 0xcdcdcdcd, so invalid.

I tried looking into how FL handles the CollisionEvent list, but it doesn’t seem to make any special case for those events, even though the second pointer obviously doesn’t work. Is there a straightforward way of identifying those “broken” events short of just trying to cast them to a CObject and seeing if it breaks?

Even better would be figuring out a way of tracing back which CBeam did it.

EDIT: So apparently if a beam weapon’s ammo has zero mass, it shows up in the CollisionEvent list, but does not refer to the proper object instance.

Gisteron, I fail to see the point. It would be much better to have the source.

What you’re saying is that it’s better to fix the car with duct tape and chewing gum than to properly repair it like a mechanic. It makes no sense.

If you were attempting to piece the game together like some others do, you’d much prefer having the source for the flexibility and ease of use that would give you.