Hi guys,
I want to help with some things I 've found so far but I don't have enough time to sign up at github and check if these bugs are already known so far.
So please don't flame me
Im using alpha 1.3 Debian-Build on a linux box.
- nuclear cells can't be found by radar. item.position has undefined values for them.
Workaround so far is taking them out of the nuclear plant by waiting 35 seconds then grab and then using them directly without any dropping in between.
- the file requester box shows files mixed, no sorting possible. I miss the ordinary headlines in order to sort by name/size/date
- sometimes reading/saving gets crumbled filenames. so LongFilename.txt gets sometimes LongFilename. or LongFilename.tx.txt
- programmes with umlauts ÖÄÜöäüß get strange characters and dont work anymore
- Changing the appearance of the Astronout leads to white rendering of him although it works later on but you cant modify things in realtime (in the meaning of youll see nothing).
- The maximum font size just looks acceptible. The min is way to small. Can you add more/bigger size like 3 more steps to maxium font size?
Suggestions for features I would like to have (maybe you too):
1. It is possible to use public functions for all bots. If the bot with the public function in its memory get's distroyed the code gets lost also...
So why not make the spaceship be able to have those public funtions in its memoy (add Programme -registers like for the bots, but code only with "public" can be used).
Then any robot can access those functions and in case of a bot being destroyed the public function code still exists.
As the SpaceShip is the base station of all so tho speak you could explain this with its communication nature and surely any remote control of any bot is being send from here.
2. A dual-screen solution would be very useful, so having the original Colobot window on screen 1 and on screen 2 you have either SatCom or the CBOT-Editor as own windows. Maybe just seperate windows for each are enough to achieve this. Also a sperate window for the "watch" (=showing variable values of any relevant information) would be a good idea. At the moment the space under the editorfield is very small.
3. Add some more screen resolutions (or free aspect so everybody can finetune to his/her own monitor).
4. I miss breakpoints in the editor for debugging. One button more like "run until breakpoint" and a seperate mark per line would be enough ... like we are used to in Microsoft VBA for example.
5. I'v got all the 58 user-developed programms that used to be on the Epsitec Homepage where they are no more accessible. Where can I send/upload them?
6. There should be a code-exchanging place. Is the wiki or this forum the place for them and especially where precisely ?
Thanks for reviving this excellent game... :love
I want to help with some things I 've found so far but I don't have enough time to sign up at github and check if these bugs are already known so far.
So please don't flame me
Im using alpha 1.3 Debian-Build on a linux box.
Code:
dpkg -l|grep colobot
ii colobot 0.1.3-1 amd64 educational programming strategy game
ii colobot-common 0.1.3-1 all educational programming strategy game - data
ii colobot-common-sounds 0.1.3-1 all educational programming strategy game - sounds and music
ii colobot-common-textures 0.1.3-1 all educational programming strategy game - textures- nuclear cells can't be found by radar. item.position has undefined values for them.
Workaround so far is taking them out of the nuclear plant by waiting 35 seconds then grab and then using them directly without any dropping in between.
- the file requester box shows files mixed, no sorting possible. I miss the ordinary headlines in order to sort by name/size/date
- sometimes reading/saving gets crumbled filenames. so LongFilename.txt gets sometimes LongFilename. or LongFilename.tx.txt
- programmes with umlauts ÖÄÜöäüß get strange characters and dont work anymore
- Changing the appearance of the Astronout leads to white rendering of him although it works later on but you cant modify things in realtime (in the meaning of youll see nothing).
- The maximum font size just looks acceptible. The min is way to small. Can you add more/bigger size like 3 more steps to maxium font size?
Suggestions for features I would like to have (maybe you too):
1. It is possible to use public functions for all bots. If the bot with the public function in its memory get's distroyed the code gets lost also...
So why not make the spaceship be able to have those public funtions in its memoy (add Programme -registers like for the bots, but code only with "public" can be used).
Then any robot can access those functions and in case of a bot being destroyed the public function code still exists.
As the SpaceShip is the base station of all so tho speak you could explain this with its communication nature and surely any remote control of any bot is being send from here.
2. A dual-screen solution would be very useful, so having the original Colobot window on screen 1 and on screen 2 you have either SatCom or the CBOT-Editor as own windows. Maybe just seperate windows for each are enough to achieve this. Also a sperate window for the "watch" (=showing variable values of any relevant information) would be a good idea. At the moment the space under the editorfield is very small.
3. Add some more screen resolutions (or free aspect so everybody can finetune to his/her own monitor).
4. I miss breakpoints in the editor for debugging. One button more like "run until breakpoint" and a seperate mark per line would be enough ... like we are used to in Microsoft VBA for example.
5. I'v got all the 58 user-developed programms that used to be on the Epsitec Homepage where they are no more accessible. Where can I send/upload them?
6. There should be a code-exchanging place. Is the wiki or this forum the place for them and especially where precisely ?
Thanks for reviving this excellent game... :love