Player Features and Ideas Discussion

How to:
- Stop all calculations in a node. Give notification that node is being remodelled, keep connections up.
- Snapshot all statuses. Split relevant solar system to a box based on #rules
- Move box that box to separate node.
- Cancel those actions that are relevant to solar system borders, I/O, gatejumps, cyno's. Give error message "brace your self" and tick timer before re initiating actions
- Resume all relevant calculations in solar system that is now in its own node.
- Start up specialized i/o-environment server.
- Start up specialized GRID management server.
- Stop all calculations in the solar system. Give message "wait a sec, CFC is cynoing in". Cancel I/O from the solar system server.
- Snapshot all statuses. Split people in relevant grid(s) to a box.
- Move this box into a GRID management server.
- Resume all relevant calculations in GRID and Solar system with synch check.
- Allow access to this GRID only through specialized I/O server. Animate with warp tunnel.
- Make all this automated behaviour
- Profit

Needed:
1.) Create dynamic server "halt" feature to allow node stop without disconnects. (afaik, already exists)
2.) Create logic for snapshot and its parse and transfer. (afaik exists, but no while node is on)
3.) Modify existing solar system level code with "if this grid is type A, if player attempts warp to, move player to I/O-server", otherwise solar system behaves as usual. (warp to this grid becomes essentially a jump to solar system)
4.) Develop a separate I/O server to manage clients coming and going from GRID. Maintain passively relevant data on I/O server, not on GRID or solar system server. Necessary for interaction purposes and to maintain synch with other EVE space while GRID on separate TIDI (basically what a gate does now, but on its separate server entity, like Tiago D'Agostini's laptop)
5.) Develop GRID server with dynamic load management (no 1 CPU limitation) for all resources, concentration only on GRID relevant calculations. Only interacts with solar system through I/O server to remove excess irrelevant-to-playability load.

Reasoning:
It's a load of work, but it's way way easier than rewriting whole EVE with assembly, cutting % units from CPU cycles, getting collision detection more performance friendly, fixing drone behaviour math., changing game mechanics etc. The only really new thing to develop is the GRID server that has dynamic load management in its structure, and heck even without dynamic load the 1 CPU now manages only 1 grid. Completing this GRID server also acts as a starting point for re-coding some of the legacy EVE, without overhauling everything.

Virtual practice:
Client warps to a grid, check if its type A, if it is, client goes to I/O server, is removed from solar system server with data about where to land on the GRID.
Client jumps to a solar system, but the landing grid is type A, goes to I/O server for placement on GRID, wets himself.
Client has a tag on local chat, but chat doesn't travel through I/O to stop GRID flooding.
I/O server has a beacon in solar system server that reacts to polls.
Client in solar system directional scans GRID, gets a list of targets from I/O server. No effect on GRID.
Probing beacon will work the same way. (Optionally I/O polls GRID for only relevant location data, ie ships gates towers and directional scanner or probes wont see drones, bubbles, POS mods. )
Using cyno or bridges will bring all travellers to I/O server for parsing and placement queue on GRID. If queue grows too long or too rapidly for GRID to manage dynamic placing without extensive TIDI, GRID will PAUSE, place new entrants, synch check and continue.

I found the problem. There was a cat5 that was chewed by a rodent. I made a new one , installed it, and tied it up out of the way.

Thatll be 105.00 for the Service Call, 56.00 for labor, 10.05 for parts and I ate a pop tart from the open package I found.

I know another much more simply way, how about don't try and bridge 700 dudes on a grid which already has approx 2500 dudes fighting, thousands of drones, a ton of bubbles and a server already at max TiDi?