Server Kicks when package bought

rsabatino

i tried to run rebalance also nice mod but. too many crashes too many

Gisteron

first mod i tried after rebalance. first mod i learned to change and how to mod at all… nice thingy but yes, buggy like hell and dreadfully unbalanced…

Bejaymac

@ Tanjitsu, A thought just struck me, what anti cheat are you running on the server and do you need/have the package listed in it.

Tanjitsu

thx for getting the topic back on track Bejaymac

no cheat stuff just standard freelancer server atm.

Bejaymac

MD included the 1.1 server patch with 3.50 full (probably had it in earlier versions aswell), and it will kick anything that isn’t part of vanilla Freelancer. You need IFSO, FLAC, FlHook etc to take control of the FLServer.exe to stop it kicking you.

Tanjitsu

Very True but…
when i took over i started by comparing RB to all the patches. i encompase them into RB, i merged in the 1.1 SDK + bits of the 1.4 patch and various other peoples fixes before starting to continue adding and fixing what already existed.

Did that to make sure u only needed Rebalance and not
Freelancer + 5 patches then rebalance

Thing i dont get is what u say is true
but the server has 0 problems with anyof the other 5 packages i created and added in, it just has a problem with the 2 freighter trader start packages.

My Pirate / freelancer packages all launch absolutly fine just on the standard 1.1 server.

Also in MP i do have Hook attached.

Tanjitsu

just ran the packages like

[Good]
nickname = trader_hull
category = shiphull
ship = li_freighter
price = 19420
ids_name = 12018
item_icon = Equipment\models\commodities\nn_icons\li_freighter.3db

[Good]
nickname = trader_package
category = ship
hull = trader_hull
addon = ge_lfr_engine_01, internal, 1
addon = li_freighter_power01, internal, 1
addon = ge_s_scanner_01, internal, 1
;addon = ge_s_tractor_01, internal, 1
;addon = shield01_mark01_fr, HpShield01, 1
;addon = SlowSmallBlue, HpRunningLight01, 1
;addon = SlowSmallBlue, HpRunningLight02, 1
;addon = SlowSmallBlue, HpRunningLight03, 1
;addon = SlowSmallBlue, HpRunningLight04, 1
;addon = contrail01, HpContrail01, 1
;addon = contrail01, HpContrail02, 1
;addon = DockingLightRedSmall, HpDockLight01, 1
;addon = DockingLightRedSmall, HpDockLight02, 1
;addon = co_gun01_mark01, HpWeapon01, 1
;addon = co_gun01_mark01, HpWeapon02, 1

still kicked me for cheating

StarTrader

If I remember rightly, it should not have let you take off without the tractor!? Can’t remember.

What on earth is going on on your setup?

What happens if you make the standard Rhino available on the same base at the same time and buy that?

Gisteron

try to make it use different internal equipment, one by one until you have the piece you have to check further.

Tanjitsu

try to make it use different internal equipment, one by one until you have the piece you have to check further.

have done that in post above commented out untill all that was left was the minimum needed to launch.

What happens if you make the standard Rhino available on the same base at the same time and buy that?

Top idea ST.

added

[Good]
nickname = lfr_hull
category = shiphull
ship = li_freighter
price = 151000
ids_name = 12002
item_icon = Equipment\models\commodities\nn_icons\li_freighter.3db

[Good]
nickname = lfr_package
category = ship
hull = lfr_hull
addon = ge_lfr_engine_01, internal, 1
addon = li_freighter_power01, internal, 1
addon = ge_s_scanner_01, internal, 1
addon = ge_s_tractor_01, internal, 1
addon = shield01_mark01_fr, HpShield01, 1
addon = SlowSmallBlue, HpRunningLight01, 1
addon = SlowSmallBlue, HpRunningLight02, 1
addon = SlowSmallBlue, HpRunningLight03, 1
addon = SlowSmallBlue, HpRunningLight04, 1
addon = contrail01, HpContrail01, 1
addon = contrail01, HpContrail02, 1
addon = DockingLightRedSmall, HpDockLight01, 1
addon = DockingLightRedSmall, HpDockLight02, 1

to the same base as the previous trader packages,
launches fine lol

copied above an pasted into space of old trader package / hull
only adjusted name of package and hull, kicks me

somet wrong with name.
FL server actually gave up propper error message for it this time

Possible cheating detected (Ship or Equipment not sold on base) by admin (b08184eb-c34c1c43-c8f0673d-91a16689)!

but the rest of packages dont have any equipment sold at there bases and they launch fine, is name or ship.

i also tried changing the cost incase cost of total equip was higher than cost to buy package but it didnt make a difference

Gisteron

show us the section from your market_ships.ini
as after a name change it kicks you, the only remaining file that can be reason for it is this.

Tanjitsu

Hey Gisteron,

[BaseGood]
base = fc01_07_Base
marketgood = trader_package, 1, 0, 1, 1, 0, 1, 1
marketgood = traders_package, 1, 0, 1, 1, 0, 1, 1
marketgood = lfr_package, 1, 0, 1, 1, 0, 1, 1

thats the what it looks like atm,

lfr_ launches with out problem

both trader_ and traders_ kick for cheating.

this is the current trader package

[Good]
nickname = trader_hull
category = shiphull
ship = li_freighter
price = 151000
ids_name = 12002
item_icon = Equipment\models\commodities\nn_icons\li_freighter.3db

[Good]
nickname = trader_package
category = ship
hull = trader_hull
addon = ge_lfr_engine_01, internal, 1
addon = li_freighter_power01, internal, 1
addon = ge_s_scanner_01, internal, 1
addon = ge_s_tractor_01, internal, 1
addon = shield01_mark01_fr, HpShield01, 1
addon = SlowSmallBlue, HpRunningLight01, 1
addon = SlowSmallBlue, HpRunningLight02, 1
addon = SlowSmallBlue, HpRunningLight03, 1
addon = SlowSmallBlue, HpRunningLight04, 1
addon = contrail01, HpContrail01, 1
addon = contrail01, HpContrail02, 1
addon = DockingLightRedSmall, HpDockLight01, 1
addon = DockingLightRedSmall, HpDockLight02, 1

set out exactly same as above lfr_package
only thing i see different are the names

Gisteron

hm, looks good. should be just fine. try to change the minimum rep (2nd digit, float, range -1 to 1) or give it a decimal zero. maybe microsoft did something wrong again, obviously you have nothing done wrong.

? Offline

I’ve been following this with interest. The obvious solution, at least to me, simply because i’ve cloned some of the original ships in my mod as well, i see the problem as the nickname entry in shiparch.

To me you’re using the same ship nickname which is why you are getting kicked. If you change it to say,

nickname = li_freighter2

for example, should work fine. The problem is the program is trying to access two ships called li_freighter which is where the issue is as i see it. It’s the reason you keep getting kicked.

To clarify the above, any ship you add to FL HAS TO HAVE a unique nickname, end of. I have around fifty variants of a freighter in my new mod with different colour schemes for the various factions i have, the reason they all work is each ship has a unique nickname. You simply cannot share nicknames.

Gisteron

its not said, that the liberty freighter entry in shiparch appears multiply. but maybe gibbon, youre right in a certain different way: maybe the anti cheat detection cannot handle it if multiple packages refer to the same ship entry.

Tanjitsu

Your right does seem to be a problem with the names Gibbon
ill try your solution although to clarify

Your saying nickname but hull or package,

it cant be the
ship = li_freighter

because im only creating packages to be used on a ship not using 2 seperate ships. there is only one li_freighter in the shiparch.ini

then 2 packages which call it,
im assuming packages cant have a problem both using same ship
i can try adding a second ship entry under a new name with same setup and see if it helps.

? Offline

That’s exactly the problem. You will need a new shiparch entry as well, should have mentioned that. Just copy the li_freighter one and name it li_freighter2 and all will be well.

StarTrader

Great, yes Gibbon is right…

Only one name will work per ship model. This is because a second entry using the same model will cause a conflict, uncertainty if you like, to FL as to which one to use.

The same with a lot of other things in FL such as material names in model .mat and ship part names in .cmp files and much more.

Having said that, it could be that the cheat detection is triggering because the two ship names are too similar also.

You could rename one as tr1_package and the second as tr2_package for a test only. Keep them short, similar long names are more likely to conflict.

Let us know what happens.

One more thing - if you decide to copy the ship model as a new model, you will have problems because of what I have indicated above (internal materials and ship part names) when the two ships are near each other by chance.

So to be fully OK you will need to copy the ship into new folders, with entirely new names, and clone the ships using FL model Cloner because that will change the internal names.

Gisteron

er what? one ship per model? bulshit! i copied all capitals and transports to a playable version keeping the original untouched. they refer to the very same models and materials, have the same collision groups and everything works fine! no, it might be that one package per ship but not one ship per model. really not, sorry.

? Offline

@ Gisteron

Why don’t you read the reply properly before flying off the handle and talking a load of rubbish.

Both ST and myself said one nickname per ship, not one model per ship for crying out loud. Each ship has to have, or come to think of it, anything in FL has to have a unique nickname. You can’t have one shiparch entry with multiple loadouts for players, for npcs yes, not for players. Therefore you need a new shiparch entry even if you use the same model but want to have multiple loadouts for players. Simple as that.