CPI (Console Packet Injection) Bugs
Posted: Sun Mar 30, 2014 1:40 pm
I cannot get anything to appear in the client by pushing packets from the console. Posting this only because we're at a point where this could really be helpful in diagnosing packets. Here's my initial bug list:
cploadfile 0 test.txt works. But if I change the test.txt packet and reload into index 0, world crashes.
cpsend {index} sends the packet to the client (Xinux confirms) but no display - I suspect it's our hacked method of entering the world, maybe the UI is not listening.
cpsend all, with only one index loaded, crashes world
Feature Requests:
cpclear to clear all loaded data so we can start again without restarting world
setip {index} per my post in World Foundation - change "clients" command to list indexed clients, and setip to that index (vs manually typing IP and Port)
More to come...
cploadfile 0 test.txt works. But if I change the test.txt packet and reload into index 0, world crashes.
cpsend {index} sends the packet to the client (Xinux confirms) but no display - I suspect it's our hacked method of entering the world, maybe the UI is not listening.
cpsend all, with only one index loaded, crashes world
Feature Requests:
cpclear to clear all loaded data so we can start again without restarting world
setip {index} per my post in World Foundation - change "clients" command to list indexed clients, and setip to that index (vs manually typing IP and Port)
More to come...