Simulation shell built from Unity. Players can plan how many stations(milk tea) wanted and the number of workers(reader). When a worker is attached to a station, the sales increase and also the pressure. When detached the worker from the station, the pressure decreases.
Now is only the shell. Game logic is illogical. But the following steps are game recording at server-side and simple report. Better game logic also depends on accumulated effect. Then return back to game design. Project development is a looping circle. Further development needs other parts and accumulation of usage. Actually, the original idea of this simulation game is for training. Games explain experience sometimes better than lecture or communication. But the investment costs more, of course.
Here are some notes deserve recording.
point tracking
UI elements depends on event queue. Game content depends more on overall scanning. Event object will automatically generated when deploy event actions (i.e. onClick()). I once accidentally added in failed item and then deleted everything I thought irrelevant. I deleted Event object.... and had to redo UI...
Position in game and on screen(UI)
Coordination of game and screen are different. It is obvious in 3D games, but ambiguous especially on top-down 2D. Converter is needed.
Clone game object and UI
It seems more reasonable to clone object from prefab. My first attempt wasn't success due to missed items. Maybe try again next time. Worker object was hidden behind the scene. This strategy also helped debugging otherwise.
Clone UI and attached it to game item is worth noting. UI should be the child of Canvas, even it was set to follow a game object. One resource mentioned Text could show up without canvas while creating Textmesh. I may try sometime. First concern is that the data type would be different from the source. I don't like keeping disposable remains. Second, my time is too scarce to spent on dealing orientation while turning. Just left it to Canvas.
Collide, trigger and static
Unity doesn't deal physics between static objects since those aren't movable. Rigidbody with static or Kinematic are off the gravity. Collision as trigger is allowing overlap. My design is basically ignoring collision while dragging. The only option I can use is Rigidbody with trigger. Only workers deal with collision.
My naming convention is Capitalize the 2nd word.... VC tirelessly trying to adjust my habit... so the code looks a little inconsistent....
Initialization
Items on the top ob object list are not always initialized first. I found it when tracking mysterious missing record. Therefore I put null check at potential 1st usage trigger.
Tracking or dependency
There are possible relationship between same objects, different objects or event triggering. My design uses list tracking to unify and simplify relation checking. It might be boring, but easy to debug. i.e., I found Unity doesn't destroy all dependent objects... My object was destroyed and moved out of lists. But the collision seems remain around dumping area and alerting error for null object.....
Comments
Post a Comment