randomly sacked

[Marshall]

Software:Universal Client
Version Number:0.46.6 and below
________________________________________________________________________
Location
zoric and sabrada
________________________________________________________________________
Description:
people have been getting randomly sacked lately. the buildings have money invested in them but people still get sacked. heres what i got while i was on zoric:

It cost you 7s to remove NukesKnight as an employee at your building
It cost you 7s to remove NukesKnight as an employee at your building
It cost you 7s to remove Priest as an employee at your building

came out of no where and i didn't sack them.
________________________________________________________________________
Steps to Replicate:
go to zoric or sabrada
get a job and wait
(may not get sacked though)

[dramaking444]

ive had this problem quite alot. i leave zoric, come back the next day expectingg to see lots of hard earned money, there isnt any money there, i look to see my jobs and they've all gone

[hedgehog]

i think this might have somethin' to do with the trading mode where a building won't pay employee salary if there's no stock, or a building's productivity being dependent on how many are employed, or a combination of both.

pre the first rule, this happened on reine2 for a bit, and then again on the last roja last january. it's entirely possible it's just somethin that pops up in specific versions, gets fixed and rebroken, but i suspect it's actually a combination of several infrequently used settings.

[Mit]

oddly enuf.. ive tracked the source of that specific message (thank you for copying the exact text, btw, Marshall, as that always helps to debug things) and that one should only get printed in response to manually sacking an employee from the building menu.

Only thing i can think of is some sort of bug that causes a mismatch of IDs and activates the manual sacking process on your building when another player is using the menu to sack employees from theres. Long shot but i dont spose you can remember if there was anyone alse around at the time who might have been doing that?

For 0.49.7 Ive added some extra security checks serverside to prevent any spurious messages being sent, which may well fix the problem - but as the menu seems to work as expected for me with simple 1-player tests, we will need to work out a way of replicating that to be able to find the root cause of the problem. If anyones in the mood for some beta-testing, then getting a couple of ppl on a world and using the 'sack employee' menu option a bit might bring it to light.