I have some questions about publishing from A6 pro. Instead of creating several threads for each, I am hoping that they could be answered all in one place.

Q1: How can I change the icon for the .exe, including running the engine in window mode and on the task bar?

Q2: How do I display specific TEXT_STDOUT content only? i.e "Searching for Servers",launching .dlls files, but not the conitec info?

Q3: How can I create .exe's specifically for -cl or -sv command line options, without resorting to bat files, shortcuts or similiar?

Q4: Is all the above legal under A6 Pro? I believe it is.

Q5: Is there a way to disable some command line options? for example -nc prevents the engine self checking for hacks; this is a risk for published games?.

Thanks in advance for any and all responses, especially if they are helpful

A1:use an icon changer to change acknex.exe and then publish;Use the GSmyICO dll
to change the task bar icon
A2:I don't own pro so I'm not sure but why dont you just use TEXT "Searching for Servers...", x, y;instead.
A3:according to me manual this should do COMMAND "-sv";
A4:I believe it is too.
A5:I don't know but but ifdef may work.

Indiglow, at entering this thread a username/password box pops up here about authorisation for "unpaid webdomain"... :P

lol for www.indiglow.co.uk

1.How can I change the icon for the .exe, including running the engine in window mode and on the task bar?
ResHacker.exe
It is not directly known whether the program effectively modifies icons for productions.
1a. Is that legal?
According to some user agreements, modifying the icon might seem to be a 'violation'.
However, if memory serves, and it often does not, JCL may have OKed that particular maneuver in one or more threads.
2. How do I display specific TEXT_STDOUT content only? i.e "Searching for Servers",launching .dlls files, but not the Conitec info?
TEXT_STDOUT is known, but not thoroughly.
Here, specific home grown functions are used to emulate stdout, or cout, to print multiple lines of debug info over entities or at specific positions and to diag output to the standard log file.
Some of those functions are freely available.
(New versions pending.)
3.How can I create .exe's specifically for -cl or -sv command line options, without resorting to bat files, shortcuts or similar?
Sorry, that is not directly known here.
4. Is all the above legal under A6 Pro? I believe it is.
1. see 1a.
2. The field of applicability seems askew for this item and the question.
3. This item was defined as a pseudo-direct unknown.
5. Is there a way to disable some command line options? for example -nc prevents the engine self checking for hacks; this is a risk for published games?
It is assumed that some command line options are for debug use only, and those options might not be accessible in the final production.
However, considering default mutability (no hacks), it seems a lean toward NO might be appropriate for that one.
The engine might not be known for its flexibility (but there's no need to cast pebbles and boulders...today).

@testDummey: Thanks for the reply.

Re:1.
I am looking at install shield to see if there is a way to change icons during install. I am puzzled that the Pro version does not seem to comfortabley accomodate this when publishing Pro content.

I recall trying to use an icon changer of some kind before and it appeared to currupt the exe. I will look at the software you suggest.

Re:2
I presume you mean a custom .dll. I will investigate this further.

Re:3
That's going to be somewhat problematic. Thanks for the concise reply.

Re:4
I am sure that when we are close to final publish, we can discuss with Conitec much of the legal implications and come to some amicable arrangement.

Re:5
Looks like another 'support' type enquiry then. Indeed the time for flinging the preverbial faeces around is not now

Thanks for all your help testDummy, much for us to investigate later.

@Bomber & Joozey: Sorry we had a mess up with our billing,problem is now resolved.

for no.3 you could
exec("myprogram.exe",""); get it to recall itself and clse down the original so all command line options are ignored except the one's you've preset in code

or you could get it to close if ones have been defined in the command options without specific requirements that you don't want to automatically close


Hope this helps

e.g

Quoting indiGLOW.

No, in that case _0c.wdl is referred to, albeit, the reference isn't obvious.
_0c.wdl is an ever-growing, mutating C-Script file stuffed with debugging (and other) junk.
A version of the file can be retrieved by following the link below.
Of course, it is probably considered undesirable by most other parties, and on the brightest side here, the reference is superfluous.



C++ is find and dandy, but no smiles for hackish, slower, diet-C.

Thanks both.

@MrGuest: Catching the command line options I don't want into a 'exit' ifdef is of course the simplest way to filter out command line options I don't want. Simple, clean and it should have been obvious!

Much Thanks

@testDummy: I can't see a link to _0c.wdl in your post?

I am building a multiplay capable system and want to allow login and switching servers in real time, so I guess the STD_OUT text I am really interested in are connecting to server / launching client etc.

If I understand the capabilities of A6 Pro correctly, I can do this within the program anyway, so the creation of a server/client UI section before fully launching the app would suffice.

Thanks for your support, and let me know if you dig out that link.

3DGS_index.html
The actual link is a few deep from the sig.
_0c.wdl
Host doesn't allow direct links.
using slooooooooow dial-up connection right now
If 'you' see ads on the page, 'your' ad blocker is not configured properly.