search

zhyrohaad / AlasiyaEvE

Public repo for bug tracking the private Alasiya-EvE codebase
2 stars 0 forks source link

Blatantly violate cargohold sizes #58

Open ryllae opened 4 years ago

ryllae commented 4 years ago

While testing #28 #37 and #57, I found a reasonably consistent way to blatently violate cargohold size restrictions.

Note: My Orca can hold 31,500K.

From an overly full (say, 1B m^3) jetcan of tritanium (just a source of mats for this bug): shift drag the stack to my orca. Reduce the number from 3150000 to 3140000, filling it all but 100m^3.

drag 27,400m^3 to the 2nd jetcan. drag that 27,400 directly ontop of the current stack in the cargo hold (asking for a new split, not a fill). type in 2740000. You now have way too much in your cargo hold. There is also a phantom stack in the 2nd jetcan (don't play with it you can crash the server).

Right click, choose stack all in the 2nd jet can to clean it up. Move another 27400m^3 from the 1st -> 2nd -> Orca as long as you want, filling your Orca with unlimited cargo.

Capture57

zhyrohaad commented 4 years ago

wow seems like inventory still has things to look over.

zhyrohaad commented 4 years ago

all container capacity checks have been fixed.

zhyrohaad commented 3 years ago

no, they havent as previously stated. so, the bug where you drop a stack directly onto another stack is definitely an exploit, but is due to coding. wasnt enough thought when determining the destination location for capacity testing. this is an easy fix, and testing now for possible other exploits or unexpected behaviour.

****quick update while testing, found few more exploits along with some unexpected denial of acceptable behavior, including the denial of moving cargo between corp hangars. working on fixes and testing.

zhyrohaad commented 3 years ago

this seems to be fixed

main is not updated as of yet.

update main has been updated